Every line below is a request this page made to the systems that run Surf. Checked .
Measured from this page, against production, with the round trip each one took.
Opening Surf at app.surfsocial.org, in a browser or as an installed app.
Operational
202 ms
The requests Surf makes to load a feed, post, reply, follow and search.
Operational
370 ms
Everything Surf stores: posts, replies, follows, messages and settings.
Operational
370 ms
Creating an account, signing in, and staying signed in.
Operational
112 ms
Getting photos, video and audio off your device and into a post.
Operational
134 ms
Serving photos, video and audio back to everyone who looks at them.
Operational
146 ms
Each bar is one day, coloured by the worst state recorded that day. Checks run every half hour, so the history records sustained trouble rather than every momentary blip, and a day with no checks recorded is left blank rather than counted as healthy. Serving build baf72ab.
Six providers Surf depends on, listed by the job each one does and reported as each one reports itself. An incident upstream frequently never reaches Surf, so nothing here changes the state above.
Runs the application itself and the scheduled jobs it hosts.
Operational
The database, sign-in, live message delivery, and the upload signer.
Operational
Media storage and delivery, live video, call relay, and the vision and speech models.
Degraded
Minor Service Outage
Checkout, subscriptions and creator payouts.
Operational
Verification email, security alerts and notification digests.
Operational
The text model behind Ask, summaries, captions and the writing tools.
Operational
The ladder the team works from, published as it is written.
Severity 1
Data is lost or exposed, or Surf is down for everyone.
We act immediately and stop the bleeding before diagnosing it.
Severity 2
A core surface is broken for everyone and no data is at risk.
We start within the hour, and roll the release back first if the break followed one.
Severity 3
One feature is degraded, or broken for some people.
We fix it forward in the next working session.
Severity 4
Internal or cosmetic, with nothing a person using Surf would notice.
It goes into the next pass.
Nothing recorded yet. When something breaks, it is written up here while it is happening and left afterwards: what broke, who it reached, when it was fixed, and what changed so it does not happen twice.
Seeing something this page is not? Tell us, and include the time it happened. For anything that is not an outage, the Help Center is the faster route.
The same report is served as JSON at /api/status.
