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 32 min ago. Last stored result reached it in 818 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 17 | 0 | 0.0 | 625 ms | 0 |
| Mon 19 | 0 | 0.0 | 513 ms | 0 |
| Mon 21 | 0 | 0.0 | 450 ms | 0 |
| Mon 23 | 0 | 0.0 | 528 ms | 0 |
| Tue 01 | 0 | 0.0 | 425 ms | 0 |
| Tue 04 | 0 | 0.0 | 677 ms | 0 |
| Tue 06 | 0 | 0.0 | 581 ms | 0 |
| Tue 08 | 0 | 0.0 | 475 ms | 0 |
| Tue 10 | 0 | 0.0 | 558 ms | 0 |
| Tue 12 | 0 | 0.0 | 403 ms | 0 |
| Tue 14 | 0 | 0.0 | 402 ms | 0 |
| Tue 17 | 0 | 0.0 | 481 ms | 0 |
| Tue 19 | 0 | 0.0 | 569 ms | 0 |
| Tue 21 | 0 | 0.0 | 481 ms | 0 |
| Tue 23 | 0 | 0.0 | 634 ms | 0 |
| Wed 02 | 0 | 0.0 | 569 ms | 0 |
| Wed 04 | 0 | 0.0 | 519 ms | 0 |
| Wed 06 | 0 | 0.0 | 692 ms | 0 |
| Wed 08 | 0 | 0.0 | 288 ms | 0 |
| Wed 11 | 0 | 0.0 | 450 ms | 0 |
| Wed 13 | 0 | 0.0 | 620 ms | 0 |
| Wed 15 | 0 | 0.0 | 455 ms | 0 |
| Wed 17 | 0 | 0.0 | 671 ms | 0 |
| Wed 19 | 0 | 0.0 | 504 ms | 0 |
| Wed 21 | 0 | 0.0 | 682 ms | 0 |
| Thu 00 | 0 | 0.0 | 632 ms | 0 |
| Thu 02 | 0 | 0.0 | 568 ms | 0 |
| Thu 04 | 0 | 0.0 | 587 ms | 0 |
| Thu 06 | 0 | 0.0 | 684 ms | 0 |
| Thu 08 | 0 | 0.0 | 505 ms | 0 |
| Thu 10 | 0 | 0.0 | 649 ms | 0 |
| Thu 12 | 0 | 0.0 | 415 ms | 0 |
| Thu 14 | 0 | 0.0 | 528 ms | 0 |
| Thu 16 | 0 | 0.0 | 726 ms | 0 |
| Thu 18 | 0 | 0.0 | 525 ms | 0 |
| Thu 20 | 0 | 0.0 | 441 ms | 0 |
| Thu 22 | 0 | 0.0 | 447 ms | 0 |
| Fri 00 | 0 | 0.0 | 667 ms | 0 |
| Fri 02 | 0 | 0.0 | 548 ms | 0 |
| Fri 05 | 0 | 0.0 | 535 ms | 0 |
| Fri 07 | 0 | 0.0 | 552 ms | 0 |
| Fri 09 | 0 | 0.0 | 669 ms | 0 |
| Fri 10 | 0 | 0.0 | 516 ms | 0 |
| Fri 12 | 0 | 0.0 | 646 ms | 0 |
| Fri 14 | 0 | 0.0 | 451 ms | 0 |
| Fri 16 | 0 | 0.0 | 665 ms | 0 |
| Fri 18 | 0 | 0.0 | 639 ms | 0 |
| Fri 19 | 0 | 0.0 | 818 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 Sered 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 Sered goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Sered alerts to Slack, Discord or a webhook — free.
Sered, at sered.net, is one of the Cloud & developer services we monitor. Hosting web, dominios, correo profesional y Cloud VPS en Sered. Crea y haz crecer tu proyecto online con soporte técnico 24/7 en español.
Sered publishes an official status page at status.sered.net; when we can read it, its incident level is folded into the status shown here.
Common problems for 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: 584 ms average, 441–818 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Sered incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
584 ms on average over the last 24 hours (441–818 ms).
Yes, at https://status.sered.net.
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 Sered here at once, the problem is on Sered'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 Sered. 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.