User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
fletcher.nl · Cloud & developer
Is Fletcher down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Wereldwijde storing treft Microsoft: Outlook en mogelijk Teams werken niet
Source: the vendor's status page · We are not affiliated with Fletcher.
What to try while Fletcher is having problems
Estimated fix: Not enough Fletcher history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–10 h; 81 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → fletcher.nl—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 47 min ago. Last stored result reached it in 1009 ms.
Official status
Minor incident
Wereldwijde storing treft Microsoft: Outlook en mogelijk Teams werken niet Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 1220 ms | 0 |
| Mon 18 | 0 | 0.0 | 1177 ms | 0 |
| Mon 21 | 0 | 0.0 | 1112 ms | 0 |
| Mon 23 | 0 | 0.0 | — | 1 |
| Tue 01 | 0 | 0.0 | 1371 ms | 0 |
| Tue 03 | 0 | 0.0 | 1039 ms | 0 |
| Tue 05 | 0 | 0.0 | 1075 ms | 0 |
| Tue 07 | 0 | 0.0 | 811 ms | 0 |
| Tue 09 | 0 | 0.0 | 864 ms | 0 |
| Tue 11 | 0 | 0.0 | 1199 ms | 0 |
| Tue 14 | 0 | 0.0 | 820 ms | 0 |
| Tue 16 | 0 | 0.0 | 859 ms | 0 |
| Tue 18 | 0 | 0.0 | 1157 ms | 0 |
| Tue 20 | 0 | 0.0 | 892 ms | 0 |
| Tue 23 | 0 | 0.0 | 1002 ms | 0 |
| Wed 01 | 0 | 0.0 | 1078 ms | 0 |
| Wed 03 | 0 | 0.0 | 1052 ms | 0 |
| Wed 05 | 0 | 0.0 | 1181 ms | 0 |
| Wed 07 | 0 | 0.0 | 1053 ms | 0 |
| Wed 08 | 0 | 0.0 | 812 ms | 0 |
| Wed 10 | 0 | 0.0 | 1021 ms | 0 |
| Wed 12 | 0 | 0.0 | 960 ms | 0 |
| Wed 14 | 0 | 0.0 | 896 ms | 0 |
| Wed 16 | 0 | 0.0 | 1367 ms | 0 |
| Wed 18 | 0 | 0.0 | 1135 ms | 0 |
| Wed 21 | 0 | 0.0 | 701 ms | 0 |
| Wed 22 | 0 | 0.0 | 755 ms | 0 |
| Thu 00 | 0 | 0.0 | 1169 ms | 0 |
| Thu 03 | 0 | 0.0 | 1122 ms | 0 |
| Thu 04 | 0 | 0.0 | 1214 ms | 0 |
| Thu 06 | 0 | 0.0 | 1053 ms | 0 |
| Thu 08 | 0 | 0.0 | 924 ms | 0 |
| Thu 10 | 0 | 0.0 | 1242 ms | 0 |
| Thu 12 | 0 | 0.0 | 1672 ms | 0 |
| Thu 15 | 0 | 0.0 | 1264 ms | 0 |
| Thu 17 | 0 | 0.0 | 1106 ms | 0 |
| Thu 19 | 0 | 0.0 | 1025 ms | 0 |
| Thu 21 | 0 | 0.0 | 1076 ms | 0 |
| Thu 23 | 0 | 0.0 | 1110 ms | 0 |
| Fri 01 | 0 | 0.0 | 749 ms | 0 |
| Fri 03 | 0 | 0.0 | 971 ms | 0 |
| Fri 05 | 0 | 0.0 | 997 ms | 0 |
| Fri 07 | 0 | 0.0 | 1091 ms | 0 |
| Fri 09 | 0 | 0.0 | 1363 ms | 0 |
| Fri 11 | 0 | 0.0 | 1097 ms | 0 |
| Fri 13 | 0 | 0.0 | 1017 ms | 0 |
| Fri 15 | 0 | 0.0 | 1122 ms | 0 |
| Fri 17 | 0 | 0.0 | 1009 ms | 0 |
Reliability
98.75%Uptime · 30 days
98.75%Uptime · 90 days
1 / 1Outages · 30 / 90 days
2 h 8 minAverage outage
98.75% 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.
Embed this status: free live Fletcher badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
Having trouble with Fletcher?
One report per service every 10 minutes from this network. No account.
Follow Fletcher
Get an email when Fletcher goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Fletcher alerts to Slack, Discord or a webhook — free.
About Fletcher
Fletcher, at fletcher.nl, is one of the Cloud & developer services we monitor. Boek met de laagste prijsgarantie bij Fletcher Hotels! Ontdek meer dan 150 uniek gelegen hotels in de mooiste steden en natuurgebieden van Nederland, Duitsland en (via partners) België.
Fletcher publishes an official status page at status.fletcher.nl; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 98.75% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 1052 ms average, 749–1363 ms range across 12 successful checks.
Questions
Is Fletcher down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Wereldwijde storing treft Microsoft: Outlook en mogelijk Teams werken niet
When was Fletcher last down?
The most recent public incident we recorded started 2026-11-09 and lasted 2 h 8 min. 1 incident since monitoring began 8 days ago.
What is Fletcher's uptime?
From our own checks: 98.75% over 8 days of checks.
How fast does Fletcher respond?
1052 ms on average over the last 24 hours (749–1363 ms).
Does Fletcher have an official status page?
Yes, at https://status.fletcher.nl.
Fletcher not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Fletcher here at once, the problem is on Fletcher'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 Fletcher. 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.