Skip to main content

System Status

Live dashboard: pay4feedback.com/status

A lightweight status page that runs three real-time health checks directly from your browser. No account needed, no login, public-facing.

What it checksโ€‹

ComponentEndpointExpected
Landing sitepay4feedback.com/HTTP 200
Dashboard APIapp.pay4feedback.com/api/healthJSON {data: {status: "ok"}}
Documentationpay4feedback.com/docs/HTTP 200

Each check measures real-user latency (what your browser actually sees), not synthetic monitoring from a datacenter somewhere. If the page is slow for you, the numbers reflect that.

Overall bannerโ€‹

The banner at the top of the status page rolls up the three component results:

  • ๐ŸŸข All systems operational โ€” all three checks green.
  • ๐ŸŸก Partial outage โ€” at least one check failing, at least one still healthy.
  • ๐Ÿ”ด Major outage โ€” all three failing.

It auto-refreshes every 30 seconds while the page is open.

Things the status page does not showโ€‹

  • Historical uptime โ€” no 30-day / 90-day graphs yet. If you need SLA-grade uptime reports for procurement, email sales@pay4feedback.com. Enterprise customers get monthly uptime summaries as part of their account review.
  • Incident timeline โ€” past incidents are not surfaced on this page. For operational transparency during a live incident, follow mailto:support@pay4feedback.com for direct updates.
  • Widget CDN health โ€” the embeddable widget is served from the landing CDN, so if the landing check is green, the widget is loading. No separate probe.
  • Tremendous payout delivery โ€” Tremendous publishes its own status at status.tremendous.com. Reward disbursement depends on their uptime, not just ours.
  • Stripe โ€” same: status.stripe.com.

If a check is failing for you but not for usโ€‹

The status page runs in your browser, so a failed check can mean:

  • Your network / corporate firewall blocks one of our domains.
  • Browser extension (ad-blocker, privacy tool) strips our requests.
  • DNS issue on your ISP's side.
  • Genuine outage on ours.

Try the checks in an incognito window with extensions disabled before assuming the worst. If it's still broken, email support@pay4feedback.com with a screenshot and your approximate location โ€” we can correlate with our AWS CloudWatch metrics.

During an incidentโ€‹

Our target response times (from the Contact & Support page):

  • Starter โ€” best-effort.
  • Growth โ€” 24 business hours for ticket acknowledgement, same-day for P1.
  • Enterprise โ€” 4 business hours, 2 hours for P1, dedicated account manager phone line.

Email support@pay4feedback.com to open a ticket. Include your tenant ID (Settings โ†’ General).