Report spike at 14:20 UTC — 5 reports over 5m. Most common: 'Not working' (80%); reports from Singapore, Malaysia and Brunei Darussalam.
No problems reported at Straw.Page right now
Problem reports for Straw.Page are at their usual level right now. The most recent incident was about 11 days ago.
reports · 24 h · /15 min
1h–15m–5m–
Straw.Page not working for you?
what people report · last 24 h
Not working100%
where from · last 24 h
no located reports in this window
outage map · last 24 h
live pulse
- social
I'm finally gonna break down and make a strawpage....18h - report🇩🇪Slow / glitchy2d
- report🇺🇸Pics - Chicago2d
- report🇺🇸Slow / glitchy - Long Beach2d
- report🇨🇦Sending / receiving3d
- report🇳🇱Can't log in - Amsterdam3d
Straw.Page outage record
all services by year →27 incidents in the past 12 months, none major.
Since 2025, down.now has recorded 27 outage days on Straw.Page; the largest was Jul 26, 2026 with 319 reports, across 29 countries.
Disruption at 06:46 UTC — 8 reports over 1m. Most common: 'Not working' (60%); most reports from the United States.
Outage — problem reports peaked at 48/15min around 20:45 UTC; 319 reports over 1h 50m. Most common: 'Not working' (53%); reports from the United States, the United Kingdom, Canada and 26 more countries.
- reports
- 319
- duration
- 1h 50m
- top problem
- Not working 53%
- most affected
- US 62% · of 9 countries
- peak
- 48 / 15 min @ 20:15 UTC
story · 3 beats
- 20:14 Problem reports started climbing at 20:14 UTC.
- 20:45 Peak at 20:45 UTC: 48/15min.
- 22:04 Problem reports faded around 22:04 UTC.
reports · 2026-07-26 · /15 min
incident timeline
- 20:14Problem reports started climbing.
- 20:45Peak: 48/15min.
- 22:04Problem reports faded.
outage map
Outage — problem reports peaked at 31/15min around 15:40 UTC; 35 reports over 9m. Most common: 'Not working' (60%); reports from the United States, Poland, Argentina and 5 more countries.
- reports
- 35
- duration
- 9m
- top problem
- Not working 60%
- most affected
- US 67% · of 8 countries
- peak
- 31 / 15 min @ 15:30 UTC
story · 3 beats
- 15:37 Problem reports started climbing at 15:37 UTC.
- 15:40 Peak at 15:40 UTC: 31/15min.
- 15:46 Problem reports faded around 15:46 UTC.
Disruption at 03:37 UTC — 27 reports over 7m. Most common: 'Not working' (74%); most reports from the United States.
22:07 UTC — Report spike , 1m
Report spike — problem reports peaked at 10/15min around 22:05 UTC; 5 reports over 1m. Most common: 'Not working' (100%); reports from Spain, Canada and the United States.
- reports
- 5
- duration
- 1m
- top problem
- Not working 100%
- most affected
- ES 33% · of 3 countries
story · 4 beats
- 22:05 Peak at 22:05 UTC: 10/15min.
- 22:07 Problem reports started climbing at 22:07 UTC.
- 22:07 Confirmed as report spike at 22:07 UTC.
- 22:08 Problem reports faded around 22:08 UTC.
20:43 UTC — Disruption , 6m
Disruption — problem reports peaked at 5/15min around 20:45 UTC; 16 reports over 6m. Most common: 'Not working' (71%); reports from the United States, Canada, the Philippines and 3 more countries.
- reports
- 16
- duration
- 6m
- top problem
- Not working 71%
- most affected
- US 46% · of 6 countries
story · 4 beats
- 20:43 Problem reports started climbing at 20:43 UTC.
- 20:45 Peak at 20:45 UTC: 5/15min.
- 20:49 Confirmed as disruption at 20:49 UTC.
- 20:49 Problem reports faded around 20:49 UTC.
04:32 UTC — Outage , 8m
Outage — problem reports peaked at 7/15min around 04:35 UTC; 41 reports over 8m. Most common: 'Not working' (54%); most reports from the United States.
- reports
- 41
- duration
- 8m
- top problem
- Not working 54%
- most affected
- US 74% · of 6 countries
story · 3 beats
- 04:32 Problem reports started climbing at 04:32 UTC.
- 04:35 Peak at 04:35 UTC: 7/15min.
- 04:40 Problem reports faded around 04:40 UTC.
Disruption at 12:44 UTC — 11 reports over 11m. Most common: 'Not working' (89%); reports from the United States, Czechia, Türkiye and 4 more countries.
Disruption at 09:26 UTC — 48 reports over 27m. Most common: 'Not working' (97%); reports from the United States, Australia, Canada and 10 more countries.
09:50 UTC — Disruption , 10m
Disruption — problem reports peaked at 21/15min; 21 reports over 10m. Most common: 'Not working' (69%); reports from the United States, Canada, Japan and 3 more countries.
- reports
- 21
- duration
- 10m
- top problem
- Not working 69%
- most affected
- US 65% · of 6 countries
- peak
- 21 / 15 min @ 09:45 UTC
05:30 UTC — Outage , 1h 41m
Outage — problem reports peaked at 37/15min; 118 reports over 1h 41m. Most common: 'Not working' (68%); most reports from the United States.
- reports
- 118
- duration
- 1h 41m
- top problem
- Not working 68%
- most affected
- US 70% · of 15 countries
- peak
- 37 / 15 min @ 05:30 UTC
03:27 UTC — Outage , 25m
Outage — problem reports peaked at 47/15min; 87 reports over 25m. Most common: 'Not working' (73%); most reports from the United States.
- reports
- 87
- duration
- 25m
- top problem
- Not working 73%
- most affected
- US 75% · of 14 countries
- peak
- 47 / 15 min @ 03:30 UTC
Outage — problem reports peaked at 32/15min; 106 reports over 50m. Most common: 'Not working' (89%); reports from the United States, the United Kingdom, Australia and 18 more countries.
- reports
- 106
- duration
- 50m
- top problem
- Not working 89%
- most affected
- US 42% · of 21 countries
- peak
- 32 / 15 min @ 09:30 UTC
Disruption at 06:31 UTC — 37 reports over 25m. Most common: 'Not working' (81%); most reports from the United States.
14:58 UTC — Outage , 43m
Outage — problem reports peaked at 21/15min; 35 reports over 43m. Most common: 'Not working' (100%); reports from the United States, the United Kingdom, Norway and 12 more countries.
- reports
- 35
- duration
- 43m
- top problem
- Not working 100%
- most affected
- US 49% · of 15 countries
- peak
- 21 / 15 min @ 15:30 UTC
12:07 UTC — Disruption , 10m
Disruption — problem reports peaked at 13/15min; 18 reports over 10m. Most common: 'Not working' (88%); reports from the United States, the Philippines, Spain and 3 more countries.
- reports
- 18
- duration
- 10m
- top problem
- Not working 88%
- most affected
- US 44% · of 6 countries
Disruption at 19:38 UTC — 12 reports over 12m. Most common: 'Not working' (80%); most reports from the United States.
Incident at 15:21 UTC — 47 reports over 28m.
Incident at 11:49 UTC — 296 reports over 1h 58m.
Incident at 18:09 UTC — 35 reports over 30m.
Incident at 09:39 UTC — scattered reports over 47m.
Incident at 16:37 UTC — scattered reports over 13m.
Incident at 17:31 UTC — scattered reports over 1h 9m.
Incident at 01:45 UTC — scattered reports over 18m.
Incident, starting at 19:17 UTC — scattered reports over 2h 40m.
Straw.Page comments
anonymous · no accountcommon questions
Is Straw.Page down right now?
Problem reports for Straw.Page are at their usual level right now. The most recent incident was about 11 days ago.
Is Straw.Page down for everyone or just me?
Right now down.now isn't seeing a broad Straw.Page outage, so the problem is most likely local to you — your connection, your device, or the app itself. Try the app on mobile data instead of Wi-Fi, then restart the router. If reports start arriving from other people, this page flips to an outage within minutes.
When did Straw.Page last go down?
The last recorded Straw.Page incident was about 11 days ago, on 2026-09-22. The outage record below has the peak time, duration and what people reported.
How can I report a problem with Straw.Page?
Use the report panel on this page and pick what's not working — it takes one tap and no account. Reports are anonymous, and they feed the live signal on this page immediately.
How does down.now know if Straw.Page is down?
Down.Now watches two crowd signals for Straw.Page — anonymous reports submitted here, and public social-media posts about it — and compares the live volume against what's normal for that hour of the day. A sustained spike above that baseline opens an incident, which is usually visible before an official confirmation. We measure what users report, not Straw.Page's servers directly.