Skip to main content
Document360 logo

Is Document360 Down?

No — Document360 is up
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

Reachable
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
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam44 ms4 ms19 ms119 ms
Chicago27 ms2 ms23 ms86 ms
San Jose87 ms4 ms26 ms157 ms
Singapore83 ms2 ms15 ms166 ms
Stockholm31 ms1 ms17 ms76 ms
Sydney137 ms1 ms9 ms169 ms
Tokyo84 ms1 ms9 ms119 ms
Toronto26 ms2 ms15 ms81 ms
We check that document360.com loads, not every feature behind it. Test it yourself

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 streak
Oct 7: no data
Oct 8: no data
Oct 9: no data
Oct 10: no data
Oct 11: no data
Oct 12: no data
Oct 13: no data
Oct 14: no data
Oct 15: no data
Oct 16: no data
Oct 17: no data
Oct 18: no data
Oct 19: no data
Oct 20: 100.00% uptime, 24 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 24 checks
Oct 7 Today
No downtime Partial Downtime Not measurable No data

Measured 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.

Test it yourself

Related services

Document360 outage FAQ

Which Document360 data center is my project in?
The one you pick on the login page. Document360's sign-in asks for a data center, European Union, United States or Canada, and its security summary places them in Azure's Western Europe, Central US and Canada Central regions. The status page reports each region as its own group, so an incident in the EU environment says little about a project hosted in the US or Canada.
Why does a newly published article show a 404 or old content?
Usually it is the cache, not an outage. Public knowledge bases are served through a Cloudflare edge cache with a window of about 10 minutes, and there is no manual purge. Add a query string such as ?refresh=1 to see the latest version. Document360 says a 404 that lasts beyond 15 to 20 minutes is a configuration issue, such as the slug, publish status or a redirect rule.
Readers see 'Sorry, you have been blocked' or error 6003. Is Document360 down?
Probably not. Document360's docs say this happens when Cloudflare flags a reader's IP address or browser user agent as suspicious, and the fix is to contact Document360 support so it can investigate. The same symptom can follow a regenerated JWT client secret that was not updated in your application, in which case you generate a new secret and update the configuration.
Will I lose knowledge base content in an outage?
Document360 backs up every project automatically each day at 00:00 UTC and stores the backups in Azure Blob Storage across multiple geographic locations, keeping them for up to 30 days. You can also take a manual backup at any time and restore articles, categories, languages or custom CSS and JavaScript from Settings, Knowledge base portal, Backup and Restore.
Is it Document360 or Microsoft Azure?
Sometimes Azure. Document360 is hosted on Microsoft Azure, and it traced a September 2026 slowdown in the EU environment to a platform-level Azure Cache for Redis incident. Later that month a connectivity issue on the Canada knowledge base site was caused by a Microsoft-initiated node upgrade that was expected to be non-disruptive, and Document360 recycled the affected nodes to resolve it.

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 403 or 429 means 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
Free plan available No credit card required