PŸUR outage on 10 November 2026

Problem reports about PŸUR rose to outage level at 20:16 Central European time on Tuesday 10 November 2026 and stayed there for 1 h 45 min.

They peaked at 140 reports in 15 minutes at 20:29, about 16 times the usual level for that time of day, and 317 reports came in while the outage lasted.

12 other services had an outage spike at the same time.

Is PŸUR down right now?

Started

20:16

Tue 10 Nov, Central European time

At outage level

1 h 45 min

Ended 22:01

Busiest 15 minutes

140

reports, at 20:29

Reports during the outage

317

Peak about 16× the usual level

Timeline

Reports from Tue 14:15 to Wed 04:15

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Same time

Other services with an outage at the same time

Their reports also reached outage level while PŸUR's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

Outage
Westpac
05:38–Wed 08:59

1,717peak reports
Outage
Fortnite
21:56–Wed 00:13

1,038peak reports
Outage
Grok
20:39–23:30

855peak reports
Outage
IRCTC
04:47–20:49

785peak reports
Outage
T-Mobile
20:50–21:33

380peak reports
Outage
Fastweb
21:46–Wed 04:36

255peak reports
Outage
Caixa Econômica Federal
10:19–20:25

216peak reports
Outage
Free
18:41–20:17

213peak reports
Outage
Bouygues Télécom
17:40–Wed 00:07

202peak reports
Outage
California Department of Motor Vehicles (DMV)
19:15–22:50

197peak reports
Outage
Vivo
15:04–Wed 04:37

168peak reports
Outage
Sunrise
13:50–22:30

156peak reports

PŸUR: live status and other outages

Check whether PŸUR is down right now: the live page shows the last 24 hours and fixes to try.

November 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

<iframe src="https://isitdownrightnow.app/embed/pyur/2026-11-10/" title="PŸUR outage on 10 November 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe>
<p><a href="https://isitdownrightnow.app/services/pyur/outages/2026-11-10/">PŸUR outage on 10 November 2026</a> from IsItDownRightNow.app</p>

Frame: the chart and numbers, as a small card

<a href="https://isitdownrightnow.app/services/pyur/outages/2026-11-10/"><img src="https://isitdownrightnow.app/share/pyur/2026-11-10.png" alt="PŸUR outage on 10 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>

Image: the same card as a picture

[![PŸUR outage on 10 November 2026](https://isitdownrightnow.app/share/pyur/2026-11-10.png)](https://isitdownrightnow.app/services/pyur/outages/2026-11-10/)

Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.