User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
Source: the vendor's status page · We are not affiliated with INFO.
Estimated fix: Not enough INFO history yet; similar Productivity outages lasted 45 min (median, typically 14 min–4 h; 27 outages).
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 935 ms.
Minor incident
Some components degraded (no active incident posted) Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 14 | 0 | 0.0 | 850 ms | 0 |
| Mon 16 | 0 | 0.0 | 632 ms | 0 |
| Mon 18 | 0 | 0.0 | 920 ms | 0 |
| Mon 20 | 0 | 0.0 | 906 ms | 0 |
| Mon 22 | 0 | 0.0 | 803 ms | 0 |
| Tue 00 | 0 | 0.0 | 854 ms | 0 |
| Tue 02 | 0 | 0.0 | 813 ms | 0 |
| Tue 04 | 0 | 0.0 | 825 ms | 0 |
| Tue 06 | 0 | 0.0 | 691 ms | 0 |
| Tue 08 | 0 | 0.0 | 835 ms | 0 |
| Tue 10 | 0 | 0.0 | 995 ms | 0 |
| Tue 12 | 0 | 0.0 | 779 ms | 0 |
| Tue 15 | 0 | 0.0 | 921 ms | 0 |
| Tue 18 | 0 | 0.0 | 858 ms | 0 |
| Tue 20 | 0 | 0.0 | 815 ms | 0 |
| Tue 22 | 0 | 0.0 | 793 ms | 0 |
| Wed 00 | 0 | 0.0 | 844 ms | 0 |
| Wed 03 | 0 | 0.0 | 555 ms | 0 |
| Wed 05 | 0 | 0.0 | 795 ms | 0 |
| Wed 07 | 0 | 0.0 | 717 ms | 0 |
| Wed 09 | 0 | 0.0 | 767 ms | 0 |
| Wed 12 | 0 | 0.0 | 784 ms | 0 |
| Wed 14 | 0 | 0.0 | 796 ms | 0 |
| Wed 16 | 0 | 0.0 | 900 ms | 0 |
| Wed 18 | 0 | 0.0 | 847 ms | 0 |
| Wed 20 | 0 | 0.0 | 965 ms | 0 |
| Wed 22 | 0 | 0.0 | 801 ms | 0 |
| Thu 01 | 0 | 0.0 | 897 ms | 0 |
| Thu 03 | 0 | 0.0 | 899 ms | 0 |
| Thu 05 | 0 | 0.0 | 623 ms | 0 |
| Thu 07 | 0 | 0.0 | 761 ms | 0 |
| Thu 09 | 0 | 0.0 | 776 ms | 0 |
| Thu 11 | 0 | 0.0 | 727 ms | 0 |
| Thu 13 | 0 | 0.0 | 862 ms | 0 |
| Thu 15 | 0 | 0.0 | 1061 ms | 0 |
| Thu 17 | 0 | 0.0 | 882 ms | 0 |
| Thu 19 | 0 | 0.0 | 717 ms | 0 |
| Thu 21 | 0 | 0.0 | 867 ms | 0 |
| Thu 23 | 0 | 0.0 | 784 ms | 0 |
| Fri 00 | 0 | 0.0 | 751 ms | 0 |
| Fri 02 | 0 | 0.0 | 794 ms | 0 |
| Fri 04 | 0 | 0.0 | 751 ms | 0 |
| Fri 06 | 0 | 0.0 | 834 ms | 0 |
| Fri 08 | 0 | 0.0 | 1005 ms | 0 |
| Fri 10 | 0 | 0.0 | 891 ms | 0 |
| Fri 11 | 0 | 0.0 | 794 ms | 0 |
| Fri 13 | 0 | 0.0 | 940 ms | 0 |
| Fri 15 | 0 | 0.0 | 935 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.
maintenance - production environments
During this maintenance all production environments will be updated with the latest available (security) patches and (minor) updates. Afterwards all related servers will be restarted. Also, maintenance on our network-infrastructure will be carried out where needed. Because of this maintenance your production environments may be unavailable for a short period of time while related servers are…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for INFO 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 INFO goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send INFO alerts to Slack, Discord or a webhook — free.
We track INFO (info.nl) as part of the Productivity group. We are INFO. We use design, data, and technology to give you tangible advice and create digital products that help your company thrive.
INFO publishes an official status page at status.info.nl; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
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: 849 ms average, 717–1005 ms range across 14 successful checks.
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Some components degraded (no active incident posted)
We have not recorded a public INFO incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
849 ms on average over the last 24 hours (717–1005 ms).
Yes, at https://status.info.nl.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report INFO here at once, the problem is on INFO'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 INFO. 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.