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 27 min ago. Last stored result reached it in 82 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 19 | 0 | 0.0 | 465 ms | 0 |
| Mon 21 | 0 | 0.0 | 434 ms | 0 |
| Mon 23 | 0 | 0.0 | 100 ms | 0 |
| Tue 02 | 0 | 0.0 | 411 ms | 0 |
| Tue 04 | 0 | 0.0 | 124 ms | 0 |
| Tue 06 | 0 | 0.0 | 508 ms | 0 |
| Tue 08 | 0 | 0.0 | 1004 ms | 0 |
| Tue 10 | 0 | 0.0 | 384 ms | 0 |
| Tue 12 | 0 | 0.0 | 511 ms | 0 |
| Tue 14 | 0 | 0.0 | 480 ms | 0 |
| Tue 17 | 0 | 0.0 | 135 ms | 0 |
| Tue 19 | 0 | 0.0 | 361 ms | 0 |
| Tue 21 | 0 | 0.0 | 46 ms | 0 |
| Tue 23 | 0 | 0.0 | 101 ms | 0 |
| Wed 02 | 0 | 0.0 | 370 ms | 0 |
| Wed 04 | 0 | 0.0 | 425 ms | 0 |
| Wed 06 | 0 | 0.0 | 691 ms | 0 |
| Wed 08 | 0 | 0.0 | 468 ms | 0 |
| Wed 11 | 0 | 0.0 | 121 ms | 0 |
| Wed 13 | 0 | 0.0 | 413 ms | 0 |
| Wed 15 | 0 | 0.0 | 103 ms | 0 |
| Wed 17 | 0 | 0.0 | 77 ms | 0 |
| Wed 19 | 0 | 0.0 | 608 ms | 0 |
| Wed 21 | 0 | 0.0 | 125 ms | 0 |
| Thu 00 | 0 | 0.0 | 132 ms | 0 |
| Thu 02 | 0 | 0.0 | 493 ms | 0 |
| Thu 04 | 0 | 0.0 | 483 ms | 0 |
| Thu 06 | 0 | 0.0 | 118 ms | 0 |
| Thu 08 | 0 | 0.0 | 430 ms | 0 |
| Thu 10 | 0 | 0.0 | 108 ms | 0 |
| Thu 12 | 0 | 0.0 | 196 ms | 0 |
| Thu 14 | 0 | 0.0 | 604 ms | 0 |
| Thu 16 | 0 | 0.0 | 500 ms | 0 |
| Thu 18 | 0 | 0.0 | 224 ms | 0 |
| Thu 20 | 0 | 0.0 | 394 ms | 0 |
| Thu 22 | 0 | 0.0 | 107 ms | 0 |
| Fri 00 | 0 | 0.0 | 361 ms | 0 |
| Fri 03 | 0 | 0.0 | 508 ms | 0 |
| Fri 05 | 0 | 0.0 | 88 ms | 0 |
| Fri 07 | 0 | 0.0 | 46 ms | 0 |
| Fri 09 | 0 | 0.0 | 463 ms | 0 |
| Fri 11 | 0 | 0.0 | 431 ms | 0 |
| Fri 13 | 0 | 0.0 | 550 ms | 0 |
| Fri 15 | 0 | 0.0 | 102 ms | 0 |
| Fri 17 | 0 | 0.0 | 807 ms | 0 |
| Fri 18 | 0 | 0.0 | 351 ms | 0 |
| Fri 20 | 0 | 0.0 | 801 ms | 0 |
| Fri 22 | 0 | 0.0 | 82 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: 345 ms average, 35–807 ms range across 15 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.
345 ms on average over the last 24 hours (35–807 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.