Document360 Outage History

Document360 is up right now

Pingoru has recorded 48 incidents for Document360: 14 in the last 12 months and 6 in the last 90 days.

Source: status.document360.com

48incidents recorded
14last 12 months
6last 90 days
7 daystypical duration

Incidents, newest first

Minor October 6, 2026 Intermittent Slowness and Timeouts in US Environment –

Started Oct 06, 2026, 08:26 AM UTC· resolved Oct 06, 2026, 08:26 AM UTC

  1. resolved Oct 06, 2026, 08:26 AM UTC

    The issue causing slowness and timeouts in the US environment has been fully resolved. Corrective actions have been applied, and service metrics have returned to baseline levels. All systems are operating normally, and we are continuing to monitor application health

Read the full incident report →

Minor September 30, 2026 Intermittent Slowness and Timeouts in EU Environment –

Started Sep 30, 2026, 12:52 PM UTC· resolved Sep 30, 2026, 12:52 PM UTC

  1. resolved Sep 30, 2026, 12:52 PM UTC

    The issue causing slowness and timeouts in the EU environment has been fully resolved. Corrective actions have been applied, and service metrics have returned to baseline levels. All systems are operating normally, and we are continuing to monitor application health

Read the full incident report →

Minor September 27, 2026 Incident in Canada Environment 25m

Started Sep 27, 2026, 10:39 PM UTC· resolved Sep 27, 2026, 11:04 PM UTC

  1. investigating Sep 27, 2026, 10:39 PM UTC

    We had an incident in Canada Environment around Sep 27, 2026, 22:39:20 UTC, were the there was connectivity issue was observed in the knowledgebase site and other services.

  2. resolved Sep 27, 2026, 11:04 PM UTC

    Based on our investigation, the issue was caused by a Microsoft-initiated node upgrade. The upgrade was expected to be silent and non-disruptive; however, it unexpectedly impacted the application. We recycled the affected nodes, and the issue has since been resolved.

Read the full incident report →

Minor September 17, 2026 Intermittent Slowness and Timeouts in EU Environment –

Started Sep 17, 2026, 10:17 AM UTC· resolved Sep 17, 2026, 10:17 AM UTC

  1. resolved Sep 17, 2026, 10:17 AM UTC

    The issue causing slowness and timeouts in the EU environment has been fully resolved. Corrective actions have been applied, and service metrics have returned to baseline levels. All systems are operating normally, and we are continuing to monitor application health

Read the full incident report →

Minor September 9, 2026 Slowness and timeouts in US environment 2h 6m

Started Sep 09, 2026, 01:24 PM UTC· resolved Sep 09, 2026, 03:30 PM UTC

  1. investigating Sep 09, 2026, 01:24 PM UTC

    We have observed spike exceptions in US environment for all application. We are investigating this issue.

  2. monitoring Sep 09, 2026, 01:35 PM UTC

    The issue was caused by a database event that resulted in a node reboot in the database cluster. Service has been restored, and the issue is now resolved. We are actively monitoring the situation to ensure

  3. resolved Sep 09, 2026, 03:30 PM UTC

    From approximately 13:15 UTC, customers in our US region experienced intermittent errors and slower than usual responses on knowledge base sites and other applications. The cause was a database availability event. The database cluster changed its primary node several times in quick succession while operating at its capacity limit. During these transitions, application services were unable to obtain database connections, and some restarted repeatedly as a result, which extended the recovery period. We have revisited the database cluster's capacity ceiling to provide additional headroom for scaling to avoid such incidents in the future.

Read the full incident report →

Minor September 8, 2026 We are experiencing slowness in EU environment kb site 1d 7h

Started Sep 08, 2026, 09:49 PM UTC· resolved Sep 10, 2026, 05:35 AM UTC

  1. investigating Sep 08, 2026, 09:49 PM UTC

    We are experiencing an incident in EU environment in KB site we are currently investigating the inicdent.

  2. monitoring Sep 08, 2026, 10:31 PM UTC

    We have implemented mitigation measures and restored the service to normal operation. Our team is actively investigating the root cause and will share an update once identified.

  3. resolved Sep 10, 2026, 05:35 AM UTC

    Root cause was sustained latency degradation on the upstream Azure Cache for Redis instance. Elevated P95/P99 round-trip times on cache operations caused connection pool saturation and thread starvation in the application tier, surfacing as intermittent request slowness and downstream timeouts once operations exceeded configured client timeout thresholds. The latency was not attributable to our workload — it originated from a platform-level Redis incident on the Azure side affecting the service backend. No configuration, deployment, or capacity change on our end contributed. Azure has remediated the underlying platform fault. Cache latency has returned to baseline, connection pools have recovered, and all services are operational with no residual error rate.

Read the full incident report →

Minor July 13, 2026 KB site rendering issue 35m

Started Jul 13, 2026, 06:22 AM UTC· resolved Jul 13, 2026, 06:57 AM UTC

  1. identified Jul 13, 2026, 06:22 AM UTC

    We identified an issue affecting the Custom CSS processing, which caused custom styles to not be applied correctly in KB site. Our team investigated the root cause and prepared a fix.

  2. resolved Jul 13, 2026, 06:57 AM UTC

    Analysis: We identified an issue affecting Custom CSS that caused custom styles to not be applied correctly in KB site. The issue was traced to a recent update in our Safe HTML guardrails, which incorrectly treated valid custom CSS as unsafe and prevented those styles from being applied. Resolved: We have updated the Safe HTML validation logic to correctly allow valid custom CSS while maintaining the intended security protections. The fix has been completed and is being rolled out to production. We will continue to monitor the deployment to ensure the issue is fully resolved and no further impact is observed.

Read the full incident report →

Minor June 23, 2026 TImeouts in EU environment –

Started Jun 23, 2026, 03:20 PM UTC· resolved Jun 23, 2026, 03:20 PM UTC

  1. resolved Jun 23, 2026, 03:20 PM UTC

    We experienced intermittent slowness and timeouts on the EU environment KB site caused by database pressure. Corrective actions have been applied and services are now stable. We are actively monitoring availability.

Read the full incident report →

Minor April 23, 2026 Time outs in EU environment 24d 10h

Started Apr 23, 2026, 06:35 PM UTC· resolved May 18, 2026, 05:31 AM UTC

  1. investigating Apr 23, 2026, 06:35 PM UTC

    We recently identified high latency and timeout errors affecting the EU Knowledge Base. Our team has stabilized the environment, and services have returned to normal. This issue was isolated strictly to the EU region."

  2. investigating May 18, 2026, 05:30 AM UTC

    The issue has been resolved.

  3. resolved May 18, 2026, 05:31 AM UTC

    The issue has been resolved

Read the full incident report →

Minor April 1, 2026 EU - Knowledge base site slowness 14d 14h

Started Apr 01, 2026, 02:26 PM UTC· resolved Apr 16, 2026, 05:11 AM UTC

  1. monitoring Apr 01, 2026, 02:26 PM UTC

    We observed a brief period of application slowness due to a sudden increase in incoming request volume. The system has now stabilized, and performance is back to normal. Impact: Users experienced temporary slow response times and timeout requests. Intermittent delays during the incident window Resolution: The system automatically recovered and stabilized as the request volume normalized. Our team has also validated that all services are functioning as expected. Current Status: The application is operating normally, and we are continuing to monitor the system closely.

  2. resolved Apr 16, 2026, 05:11 AM UTC

    The systems are now operational and the issue is now resolved.

Read the full incident report →

Minor March 29, 2026 EU - Application slowness and timeout 18d 1h

Started Mar 29, 2026, 03:25 AM UTC· resolved Apr 16, 2026, 05:11 AM UTC

  1. identified Mar 29, 2026, 03:25 AM UTC

    We’ve identified an issue in EU environment causing slower-than-usual response times within the application. Our team is actively working on a fix, and we appreciate your patience.

  2. monitoring Mar 29, 2026, 03:32 AM UTC

    We’ve identified that a recent update to our caching system caused the slowdown. We’ve taken steps to address this and are keeping a close watch on the service to make sure everything stays running smoothly.

  3. resolved Apr 16, 2026, 05:11 AM UTC

    The systems are now operational and the issue is now resolved.

Read the full incident report →

Minor March 5, 2026 Knowledge base site slowness –

Started Mar 05, 2026, 11:20 PM UTC· resolved Mar 05, 2026, 11:20 PM UTC

  1. resolved Mar 05, 2026, 11:20 PM UTC

    The issue was caused due to high volume of requests in specific pattern we have taken measures to mitigate this in future.

Read the full incident report →

Minor February 17, 2026 High response time for KB sites in EU Environment 6d 13h

Started Feb 17, 2026, 10:11 AM UTC· resolved Feb 24, 2026, 12:00 AM UTC

  1. investigating Feb 17, 2026, 10:11 AM UTC

    We have noticed an incident in EU Knowledge base site, the service has been stabilized now we are currently investigating the issue.

  2. resolved Feb 24, 2026, 12:00 AM UTC

    The issue was the result of a db cluster change which resulted in temporary connection issue. We will be taking steps to improve the connection resilience to avoid such incidents in the future.

Read the full incident report →

Minor November 18, 2025 CDN issue 9h 14m

Started Nov 18, 2025, 11:46 AM UTC· resolved Nov 18, 2025, 09:00 PM UTC

  1. investigating Nov 18, 2025, 11:46 AM UTC

    We are currently facing an issue with Cloudflare, where several services are incorrectly displayed as down even though they remain operational. This is a Cloudflare-related problem, and our team is actively monitoring the situation

  2. investigating Nov 18, 2025, 11:54 AM UTC

    All our services are impacted due to the Cloudflare incident, we are monitoring the situation. Cloudflare has acknowledge the issue and is working on mitigation. Cloudflare status link : https://www.cloudflarestatus.com

  3. monitoring Nov 18, 2025, 12:55 PM UTC

    Most services are now online, some may face occasional slowness. Traffic performance is steadily improving as Cloudflare services are restored. Cloudflare status: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  4. resolved Nov 18, 2025, 09:00 PM UTC

    Cloudflare has confirmed the issue has resolved and all our services have been working without any issue, hence closing this issue.

Read the full incident report →

Minor November 3, 2025 Slowness in EU environment 3h 55m

Started Nov 03, 2025, 07:35 AM UTC· resolved Nov 03, 2025, 11:30 AM UTC

  1. monitoring Nov 03, 2025, 07:35 AM UTC

    The knowledge base site version 2 has observed a slowness in and spike in response time. Based on our analysis this is due high CPU consumption, we have taken mitigation measure to scale up and bring down resource consumption. We are currently monitoring the situation.

  2. resolved Nov 03, 2025, 11:30 AM UTC

    Post-incident analysis revealed the CPU spike was triggered by a sustained influx of low-threshold malicious payloads that evaded detection by the existing WAF and DoS mitigation layers. The threat actor exploited gaps in rule sensitivity, bypassing anomaly scoring mechanisms. Mitigation involved reinforcing WAF heuristics, implementing adaptive rate-limiting. Current Status: All systems have been stabilized and are operating normally with no residual impact.

Read the full incident report →

Minor October 16, 2025 Intermittent slowness - US environment 11d 5h

Started Oct 16, 2025, 06:47 PM UTC· resolved Oct 28, 2025, 12:00 AM UTC

  1. investigating Oct 16, 2025, 06:47 PM UTC

    We encountered an issue with our database in US environment and have temporarily mitigated it by force-scaling the server. The situation is currently being monitored closely.

  2. monitoring Oct 16, 2025, 06:51 PM UTC

    The services are stable in US environment now and we are monitoring the issue

  3. resolved Oct 28, 2025, 12:00 AM UTC

    The issue was resolved by performing a forced scale-up. We have also implemented measures to ensure that scale-up operations are triggered even in edge cases involving resource constraints.

Read the full incident report →

Minor August 22, 2025 Slowness and timeout in US environment 1d 7h

Started Aug 22, 2025, 10:11 PM UTC· resolved Aug 24, 2025, 05:48 AM UTC

  1. investigating Aug 22, 2025, 10:11 PM UTC

    We are experience slowness and timeouts for applications in US environment. The issue seem to be originated due to slowness from redis.

  2. monitoring Aug 22, 2025, 10:34 PM UTC

    All the services are operational now and we are monitoring the situation.

  3. resolved Aug 24, 2025, 05:48 AM UTC

    This incident was caused due to redis connectivity issue as a result of node upgrades. This issue is now resolved and services are fully operational.

Read the full incident report →

Minor July 7, 2025 Slowness and time out in EU KB site version 2 15h 49m

Started Jul 07, 2025, 11:13 AM UTC· resolved Jul 08, 2025, 03:02 AM UTC

  1. monitoring Jul 07, 2025, 11:13 AM UTC

    Some of our customers in the EU region have experienced slowness and timeouts on the KB site (version 2). The issue has been mitigated, and we are currently monitoring the situation to ensure stability.

  2. monitoring Jul 07, 2025, 07:05 PM UTC

    We have observed some intermittent slowness in EU region due to Redis fail over event. The apps are stable now we are monitoring the situation.

  3. resolved Jul 08, 2025, 03:02 AM UTC

    The application health is back to normal. And we are closing this incident.

Read the full incident report →

Minor June 30, 2025 Slowness and Time out in KB Site 4d 2h

Started Jun 30, 2025, 12:47 PM UTC· resolved Jul 04, 2025, 02:48 PM UTC

  1. monitoring Jun 30, 2025, 12:47 PM UTC

    Some of our customers experienced slowness and timeouts on the Knowledge Base site due to one of our service instances entering an unhealthy state. The affected instance was recycled, and the service has since been restored to normal operation. We are actively monitoring the situation to ensure continued stability.

  2. resolved Jul 04, 2025, 02:48 PM UTC

    The issue causing intermittent slowness and timeouts for some customers accessing Knowledge Base sites in EU region has been resolved. It was addressed through make changes to the auto-scaling configurations to manage traffic load and targeted fixes to mitigate the impact of abnormal traffic patterns.

Read the full incident report →

Minor June 23, 2025 Service Disruption in EU Knowledge base site V2 –

Started Jun 23, 2025, 08:04 AM UTC· resolved Jun 23, 2025, 08:04 AM UTC

  1. resolved Jun 23, 2025, 08:04 AM UTC

    The service disruption was caused by a sudden surge in application usage. We have identified the potential cause and fixed the issue.

Read the full incident report →

Minor June 23, 2025 Slowness in APIHub 7d 4h

Started Jun 23, 2025, 08:03 AM UTC· resolved Jun 30, 2025, 12:46 PM UTC

  1. monitoring Jun 23, 2025, 08:03 AM UTC

    We experienced some slowness in API Hub. The issue has been mitigated for now, and we are investigating the root cause.

  2. resolved Jun 30, 2025, 12:46 PM UTC

    The API Hub is now stable, closing this issue after monitoring.

Read the full incident report →

Minor March 18, 2025 Slowness in KB site and API Hub 1h 7m

Started Mar 18, 2025, 12:20 PM UTC· resolved Mar 18, 2025, 01:27 PM UTC

  1. investigating Mar 18, 2025, 12:20 PM UTC

    We experienced some slowness in Knowledge base site and API Hub. The issue has been mitigated for now, and we are actively investigating the root cause.

  2. resolved Mar 18, 2025, 01:27 PM UTC

    We observed a failover event in Redis that lasted for a few minutes, causing slowness in KB and APIHub. All applications are functioning as expected now.

Read the full incident report →