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.
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 651 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 07 | 0 | 0.0 | 825 ms | 0 |
| Tue 09 | 0 | 0.0 | 641 ms | 0 |
| Tue 11 | 0 | 0.0 | 599 ms | 0 |
| Tue 14 | 0 | 0.0 | 958 ms | 0 |
| Tue 16 | 0 | 0.0 | 729 ms | 0 |
| Tue 18 | 0 | 0.0 | 899 ms | 0 |
| Tue 20 | 0 | 0.0 | 679 ms | 0 |
| Tue 23 | 0 | 0.0 | 739 ms | 0 |
| Wed 01 | 0 | 0.0 | 643 ms | 0 |
| Wed 03 | 0 | 0.0 | 799 ms | 0 |
| Wed 05 | 0 | 0.0 | 968 ms | 0 |
| Wed 08 | 0 | 0.0 | 684 ms | 0 |
| Wed 10 | 0 | 0.0 | 828 ms | 0 |
| Wed 12 | 0 | 0.0 | 625 ms | 0 |
| Wed 14 | 0 | 0.0 | 788 ms | 0 |
| Wed 16 | 0 | 0.0 | 599 ms | 0 |
| Wed 19 | 0 | 0.0 | 667 ms | 0 |
| Wed 21 | 0 | 0.0 | 665 ms | 0 |
| Wed 23 | 0 | 0.0 | 757 ms | 0 |
| Thu 01 | 0 | 0.0 | 550 ms | 0 |
| Thu 03 | 0 | 0.0 | 955 ms | 0 |
| Thu 05 | 0 | 0.0 | 838 ms | 0 |
| Thu 07 | 0 | 0.0 | 659 ms | 0 |
| Thu 09 | 0 | 0.0 | 645 ms | 0 |
| Thu 11 | 0 | 0.0 | 821 ms | 0 |
| Thu 14 | 0 | 0.0 | 899 ms | 0 |
| Thu 16 | 0 | 0.0 | 683 ms | 0 |
| Thu 18 | 0 | 0.0 | 594 ms | 0 |
| Thu 20 | 0 | 0.0 | 801 ms | 0 |
| Thu 22 | 0 | 0.0 | 579 ms | 0 |
| Fri 00 | 0 | 0.0 | 668 ms | 0 |
| Fri 02 | 0 | 0.0 | 768 ms | 0 |
| Fri 04 | 0 | 0.0 | 633 ms | 0 |
| Fri 06 | 0 | 0.0 | 632 ms | 0 |
| Fri 08 | 0 | 0.0 | 651 ms | 0 |
| Fri 10 | 0 | 0.0 | 718 ms | 0 |
| Fri 11 | 0 | 0.0 | 854 ms | 0 |
| Fri 13 | 0 | 0.0 | 648 ms | 0 |
| Fri 15 | 0 | 0.0 | 774 ms | 0 |
| Fri 17 | 0 | 0.0 | 653 ms | 0 |
| Fri 18 | 0 | 0.0 | 644 ms | 0 |
| Fri 19 | 0 | 0.0 | 985 ms | 0 |
| Fri 21 | 0 | 0.0 | 777 ms | 0 |
| Fri 23 | 0 | 0.0 | 793 ms | 0 |
| Sat 00 | 0 | 0.0 | 973 ms | 0 |
| Sat 02 | 0 | 0.0 | 493 ms | 0 |
| Sat 05 | 0 | 0.0 | 650 ms | 0 |
| Sat 07 | 0 | 0.0 | 629 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 Xenon Bot 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 Xenon Bot goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Xenon Bot alerts to Slack, Discord or a webhook — free.
Xenon Bot, at xenon.bot, is one of the Social services we monitor. Xenon saves your Discord server's channels, roles, and settings and restores them on any server in one command. Free to add, with thousands of server templates.
Xenon Bot publishes an official status page at status.xenon.bot; 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.
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: 734 ms average, 493–985 ms range across 18 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Xenon Bot incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
734 ms on average over the last 24 hours (493–985 ms).
Yes, at https://status.xenon.bot.
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 Xenon Bot here at once, the problem is on Xenon Bot'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 Xenon Bot. 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.