User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 88 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:15 | 0 | 0.0 | 430 ms | 0 |
| 10:30 | 0 | 0.0 | 108 ms | 0 |
| 12:30 | 0 | 0.0 | 196 ms | 0 |
| 14:30 | 0 | 0.0 | 604 ms | 0 |
| 16:45 | 0 | 0.0 | 500 ms | 0 |
| 18:45 | 0 | 0.0 | 224 ms | 0 |
| 20:45 | 0 | 0.0 | 394 ms | 0 |
| 22:45 | 0 | 0.0 | 107 ms | 0 |
| 00:45 | 0 | 0.0 | 361 ms | 0 |
| 03:00 | 0 | 0.0 | 508 ms | 0 |
| 05:00 | 0 | 0.0 | 88 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Super Publishing yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Super Publishing goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Super Publishing alerts to Slack, Discord or a webhook — free.
Super Publishing is listed in our Cloud & developer category and checked at super.so. Create a custom website in less than a minute with instant page loads, SEO optimization, and customized theming. All your content is kept and managed in Notion so you can focus on creating while Super handles the rest.
Super Publishing publishes an official status page at status.super.so; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 344 ms average, 88–869 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Super Publishing incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
344 ms on average over the last 24 hours (88–869 ms).
Yes, at https://status.super.so.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Super Publishing here at once, the problem is on Super Publishing's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Super Publishing. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.