AwwURL logo

Is Xn--b1aew down right now?

Partial outage  since 12:28 UTC
Xn--b1aew is having problems. It failed from 5 of 6 locations and loaded from the rest, so it depends where you are.

No one has reported a problem in the last hour.

🇺🇸Phoenix✕🇿🇦Cape Town✕🇸🇬Singapore✕🇫🇷Paris✕🇺🇸San Francisco✕🇮🇳Mumbai✓8s
Checked 4 h ago · 7 locations · this page updates by itself while it is open
Locations checked · 12:28 UTC
1 of 6 loaded it
fastest response 3.71 s
Official status page
None published
we look for status.xn--b1aew.xn--p1ai automatically
Visitor reports, last hour
0
normal for this hour: about 3

About Xn--b1aew

It ranks #18,057 among the most visited sites in the world on the Tranco list.

The current problem is a partial outage that began on 28 October 2026 at 12:28 UTC and is still ongoing. There have been 7 incidents in the last 90 days, 88 h 6 min of downtime in total, and 43.93% of our checks succeeded.

Your connection
Testing from your browser…
This test runs in your browser and compares with our servers. Nothing about you is stored.

Reports, last 24 hours

0 reports · normally about 3 per hour
16:46 yesterdaynow
Problem reportedNo reports in the last 24 hours.
What is not working?

Get notified

One email when xn--b1aew.xn--p1ai goes down and one when it recovers. No account needed; unsubscribe from any email.

What we checked

12:28:15 UTC
LayerResultOutcome
DNS name lookupxn--b1aew.xn--p1ai resolves to 185.6.47.15pass
TLS certificateNo certificate read yet–
HTTP, PhoenixTimed out 5 h agofail
HTTP, Cape TownTimed out 4 h agofail
HTTP, SingaporeTimed out 4 h agofail
HTTP, ParisTimed out 4 h agofail
HTTP, San FranciscoTimed out 4 h agofail
HTTP, MumbaiHTTP 0 in 7.96 s · Reachable; the server accepted the connection but sent no page, which is how some sites treat automated visitors · via bom1 4 h agopass
ContentNo page title captured–
ReputationRun the trust check–

Outage history, 90 days

43.93% uptime · 7 incidents
Started (UTC)IncidentDuration
2026-10-28 12:28Partial outage · Phoenix: Timed out; San Francisco: Timed outongoing
2026-10-11 14:20Down · Paris: Timed out; San Francisco: Timed out4 h 23 min
2026-10-08 01:42Partial outage · Phoenix: Timed out; Singapore: Timed out; Cape Town: Timed out; Paris: Timed out; San Francisco: Timed out20 h 43 min
2026-10-05 01:02Down · Phoenix: Timed out; United States: curl exit 28000, HTTP 000; Cape Town: Timed out; Mumbai: Timed out; Paris: Timed out;6 h 44 min
2026-10-03 21:38Down · Phoenix: Timed out; United States: curl exit 28000, HTTP 00013 h 19 min
2026-10-01 06:37Partial outage · Phoenix: Timed out; Cape Town: Timed out; Paris: Timed out; San Francisco: Timed out12 h 47 min
2026-09-30 00:26Down · Phoenix: Timed out; United States: curl exit 28000, HTTP 00030 h 8 min

Common questions

Is Xn--b1aew down for everyone or just me?

Compare the test from your browser above with our server checks. If our servers reach xn--b1aew.xn--p1ai and your browser cannot, the problem is on your connection, DNS or network. If both fail, the site is down.

How do you know if Xn--b1aew is down?

We request the homepage from 7 locations, check DNS, the TLS certificate and the HTTP response, and compare the page content with what we saw before. We also read the service's official status feed where one exists and count visitor reports against the usual rate for the hour.

What can I do while it is down?

Subscribe to the alert on this page and we will email you when it recovers. Clearing your DNS cache or switching networks only helps when our servers can reach the site and your browser cannot.

Related status pages