User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Social
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.
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 293 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 321 ms | 0 |
| Mon 17 | 0 | 0.0 | 325 ms | 0 |
| Mon 19 | 0 | 0.0 | 377 ms | 0 |
| Mon 21 | 0 | 0.0 | 465 ms | 0 |
| Mon 23 | 0 | 0.0 | 238 ms | 0 |
| Tue 01 | 0 | 0.0 | 255 ms | 0 |
| Tue 03 | 0 | 0.0 | 307 ms | 0 |
| Tue 06 | 0 | 0.0 | 293 ms | 0 |
| Tue 08 | 0 | 0.0 | 353 ms | 0 |
| Tue 10 | 0 | 0.0 | 338 ms | 0 |
| Tue 12 | 0 | 0.0 | 478 ms | 0 |
| Tue 14 | 0 | 0.0 | 332 ms | 0 |
| Tue 17 | 0 | 0.0 | 455 ms | 0 |
| Tue 19 | 0 | 0.0 | 166 ms | 0 |
| Tue 21 | 0 | 0.0 | 212 ms | 0 |
| Tue 23 | 0 | 0.0 | 288 ms | 0 |
| Wed 01 | 0 | 0.0 | 410 ms | 0 |
| Wed 04 | 0 | 0.0 | 287 ms | 0 |
| Wed 06 | 0 | 0.0 | 241 ms | 0 |
| Wed 08 | 0 | 0.0 | 297 ms | 0 |
| Wed 11 | 0 | 0.0 | 354 ms | 0 |
| Wed 13 | 0 | 0.0 | 239 ms | 0 |
| Wed 15 | 0 | 0.0 | 264 ms | 0 |
| Wed 17 | 0 | 0.0 | 330 ms | 0 |
| Wed 19 | 0 | 0.0 | 311 ms | 0 |
| Wed 21 | 0 | 0.0 | 278 ms | 0 |
| Wed 23 | 0 | 0.0 | 474 ms | 0 |
| Thu 02 | 0 | 0.0 | 254 ms | 0 |
| Thu 04 | 0 | 0.0 | 282 ms | 0 |
| Thu 06 | 0 | 0.0 | 331 ms | 0 |
| Thu 08 | 0 | 0.0 | 247 ms | 0 |
| Thu 10 | 0 | 0.0 | 339 ms | 0 |
| Thu 12 | 0 | 0.0 | 448 ms | 0 |
| Thu 14 | 0 | 0.0 | 253 ms | 0 |
| Thu 16 | 0 | 0.0 | 306 ms | 0 |
| Thu 18 | 0 | 0.0 | 237 ms | 0 |
| Thu 20 | 0 | 0.0 | 439 ms | 0 |
| Thu 22 | 0 | 0.0 | 352 ms | 0 |
| Fri 00 | 0 | 0.0 | 315 ms | 0 |
| Fri 02 | 0 | 0.0 | 543 ms | 0 |
| Fri 04 | 0 | 0.0 | 386 ms | 0 |
| Fri 06 | 0 | 0.0 | 469 ms | 0 |
| Fri 08 | 0 | 0.0 | 237 ms | 0 |
| Fri 10 | 0 | 0.0 | 590 ms | 0 |
| Fri 11 | 0 | 0.0 | 278 ms | 0 |
| Fri 12 | 0 | 0.0 | 514 ms | 0 |
| Fri 14 | 0 | 0.0 | 265 ms | 0 |
| Fri 16 | 0 | 0.0 | 293 ms | 0 |
No outages on record for Selmo 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 Selmo goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Selmo alerts to Slack, Discord or a webhook — free.
We track Selmo (selmo.io) as part of the Social group. Uporządkuj swoją sprzedaż w social mediach i realizuj więcej zamówień
Selmo publishes an official status page at status.selmo.io; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with social services: feeds not loading, posts or messages not sending, and login loops.
Response time over the last 24 hours: 378 ms average, 237–590 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
378 ms on average over the last 24 hours (237–590 ms).
Yes, at https://status.selmo.io.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For social services, watch for feeds not loading, posts or messages not sending, and login loops. If many people report Selmo here at once, the problem is on Selmo'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 Selmo. 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.