- Service Status
- /
- Document360

Is Document360 Down?
- Document360's status page
- Not available · we could not read it
- FlareWarden checks
- Website reachable · 8 of 8 regions · 132 ms
Right now
We could not read Document360's status page, so the verdict rests on our checks. Check it yourself How we decide
FlareWarden checks
document360.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 132 ms
- Checked
By region
- Amsterdam reachable, 133 ms
- Chicago reachable, 96 ms
- San Jose reachable, 172 ms
- Singapore reachable, 175 ms
- Stockholm reachable, 85 ms
- Sydney reachable, 177 ms
- Tokyo reachable, 128 ms
- Toronto reachable, 92 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 44 ms | 4 ms | 19 ms | 119 ms |
| Chicago | 27 ms | 2 ms | 23 ms | 86 ms |
| San Jose | 87 ms | 4 ms | 26 ms | 157 ms |
| Singapore | 83 ms | 2 ms | 15 ms | 166 ms |
| Stockholm | 31 ms | 1 ms | 17 ms | 76 ms |
| Sydney | 137 ms | 1 ms | 9 ms | 169 ms |
| Tokyo | 84 ms | 1 ms | 9 ms | 119 ms |
| Toronto | 26 ms | 2 ms | 15 ms | 81 ms |
History
Document360 website availability
Measured by FlareWarden · document360.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 425ms
Last 30 days
17-day clean streakMeasured by FlareWarden's own checks of document360.com from multiple regions every 6 hours. Document360's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Document360 does
Document360 is a knowledge base platform for publishing documentation to customers and employees, including API references. Writers create, organize and publish content in the Knowledge base portal, and readers see it on the Knowledge base site, on a Document360 subdomain or a custom domain. Each project is hosted in one data center, European Union, United States or Canada, on Microsoft Azure behind Azure CDN and Cloudflare.
What an outage looks like
Knowledge base sites load slowly, time out or return errors, usually in one region: in September 2026 a US database failover caused intermittent errors on knowledge base sites, and an Azure Redis fault slowed the EU knowledge base site. Some incidents also slowed API Hub. A 'Sorry, you have been blocked' page or error 6003 is usually Cloudflare flagging one IP address or browser, not an outage.
What to do about it
Open status.document360.com and find your data center: Europe, US and Canada each have their own Knowledge base, Portal, Portal API, API Hub and User Authentication rows, and recent incidents named a single region. If only some readers are blocked, ask Document360 support to check their IP or browser. Raise tickets at support.document360.com; support runs 24 hours on weekdays, with weekend cover for Urgent and High severity tickets.
Is it down for everyone, or just you?
If this page says Document360 is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Document360 outage FAQ
Which Document360 data center is my project in?
Why does a newly published article show a 404 or old content?
Readers see 'Sorry, you have been blocked' or error 6003. Is Document360 down?
Will I lose knowledge base content in an outage?
Is it Document360 or Microsoft Azure?
How we measure this
- We request Document360's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Document360 publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Document360 itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.
Get alerted when Document360 goes down
We check Document360 every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring


