Meta tags:
Headings (most frequently used words):
in, operational, slowness, portal, site, and, environment, us, api, eu, kb, down, base, service, knowledge, authentication, hub, intermittent, timeouts, issue, time, disruption, knowledgebase, document360, user, false, alert, instance, is, incidents, canada, rendering, timeout, high, response, out, private, projects, outage, azure, interruption, all, systems, subscribe, to, updates, status, maintenance, europe, incident, we, are, experiencing, outs, application, for, sites, cdn, version, apihub, v2, degradation, facing, got, knowlege, home, page, analytics, services, customer, website, downtime, certificate, dns, issues, public, affected, components,
Text of the page (most frequently used words):
the (277), and (155), uptime (135), 2026 (132), 100 (120), 000 (120), nov (115), gmt (93), are (86), issue (85), our (77), resolved (69), have (50), this (49), slowness (47), service (41), #portal (41), for (39), monitoring (38), environment (37), was (35), services (34), site (33), history (31), now (31), has (31), show (30), incident (28), identified (27), operational (27), caused (25), been (25), azure (24), 2025 (24), timeouts (23), api (22), cause (22), base (21), document360 (20), investigating (20), knowledge (20), 2024 (20), currently (19), team (19), that (19), disruption (18), application (18), customers (18), situation (18), all (17), system (17), with (16), status (16), experienced (16), some (16), jul (16), over (16), authentication (15), actively (15), database (15), past (15), days (15), causing (14), you (14), root (14), intermittent (14), down (13), will (13), open (13), observed (13), during (13), scaling (13), your (12), outage (12), due (12), impact (12), 2023 (12), any (12), support (12), time (12), monitor (12), working (11), feb (11), update (11), alert (11), mitigation (11), out (11), systems (11), hub (11), sep (11), page (10), response (10), may (10), closed (10), false (10), region (10), ensure (10), requests (10), high (10), server (10), from (9), normal (9), knowledgebase (9), which (9), resolution (9), traffic (9), please (8), aug (8), affecting (8), back (8), being (8), instance (8), mar (8), measures (8), further (8), analysis (8), not (8), user (8), availability (8), connection (8), incidents (8), jun (8), cloudflare (8), times (7), experiencing (7), change (7), utc (7), stable (7), fully (7), home (7), had (7), surge (7), understanding (7), performance (7), future (7), private (7), degradation (7), redis (7), applied (7), address (6), 2019 (6), issues (6), apr (6), facing (6), servers (6), functioning (6), sql (6), more (6), connectivity (6), taken (6), investigation (6), analytics (6), cluster (6), node (6), load (6), continued (6), should (6), increased (6), potential (6), identity (6), timeout (6), mitigated (6), operating (6), custom (6), monitors (6), updates (5), https (5), there (5), oct (5), infrastructure (5), one (5), dns (5), restored (5), accessing (5), sites (5), however (5), once (5), latency (5), resources (5), after (5), apologize (5), reach (5), impacting (5), volume (5), resulted (5), process (5), thank (5), inquiries (5), additional (5), information (5), hesitate (5), steps (5), periods (5), february (5), minutes (5), machines (5), closing (5), event (5), applications (5), health (5), stabilized (5), normally (5), returned (5), fixed (4), inconvenience (4), delayed (4), dec (4), investigated (4), progress (4), 2020 (4), customer (4), closely (4), related (4), users (4), 2022 (4), downtime (4), platform (4), europe (4), provide (4), when (4), recent (4), underlying (4), stability (4), ping (4), url (4), period (4), triggered (4), data (4), other (4), such (4), pages (4), next (4), operations (4), prevent (4), require (4), affected (4), also (4), usage (4), sudden (4), resulting (4), projects (4), ist (4), peak (4), horizontal (4), were (4), implemented (4), resource (4), fix (4), expected (4), virtual (4), continuing (4), corrective (4), actions (4), css (4), baseline (4), maintenance (3), higher (3), apis (3), problem (3), while (3), keep (3), here (3), jan (3), shortly (3), 2021 (3), cloud (3), com (3), microsoft (3), certificate (3), resolving (3), resolve (3), configuration (3), operation (3), summary (3), business (3), treated (3), state (3), automatic (3), recovery (3), seamless (3), comprehensive (3), enhance (3), reliability (3), auto (3), these (3), loads (3), disruptions (3), who (3), mode (3), approximately (3), increase (3), connections (3), mitigating (3), engaged (3), reliable (3), experience (3), even (3), appreciate (3), patience (3), dedicated (3), subsequent (3), determined (3), characterized (3), its (3), temporary (3), production (3), multiple (3), using (3), mechanisms (3), manage (3), threshold (3), share (3), since (3), apihub (3), version (3), result (3), scale (3), spike (3), current (3), central (3), backend (3), request (3), styles (3), correctly (3), capacity (3), cache (3), metrics (3), levels (3), canada (3), email (2), subscribe (2), aware (2), public (2), moment (2), auth0 (2), login (2), outages (2), technical (2), posted (2), instances (2), hosted (2), everything (2), rendering (2), link (2), website (2), running (2), encountering (2), waiting (2), same (2), interruption (2), network (2), rolled (2), level (2), conducting (2), earlier (2), today (2), positive (2), specified (2), confusion (2), questions (2), concerns (2), insights (2), feedback (2), improve (2), processes (2), beginning (2), november (2), highest (2), priority (2), rca (2), report (2), nodes (2), unhealthy (2), incoming (2), processing (2), leading (2), configured (2), articles (2), tier (2), ensured (2), conclusion (2), implementing (2), necessary (2), got (2), restoring (2), configurations (2), worked (2), patterns (2), taking (2), contact (2), set (2), inaccessibility (2), would (2), consistently (2), seconds (2), unusually (2), influx (2), turn (2), revealed (2), thread (2), attributable (2), pool (2), starvation (2), led (2), elevated (2), initiated (2), measure (2), demand (2), identify (2), areas (2), improvement (2), similar (2), resilience (2), continuously (2), enhancing (2), between (2), encountered (2), limit (2), write (2), delay (2), occurred (2), disrupting (2), duration (2), persisted (2), 185 (2), total (2), interruptions (2), activated (2), reached (2), critical (2), exacerbated (2), challenge (2), solution (2), vertically (2), core (2), capable (2), handling (2), adjustment (2), ensures (2), improved (2), thereby (2), limitations (2), improving (2), provided (2), monitored (2), failover (2), lasted (2), few (2), recycled (2), make (2), mitigate (2), originated (2), based (2), cpu (2), consumption (2), sustained (2), waf (2), rate (2), residual (2), several (2), incorrectly (2), impacted (2), www (2), cloudflarestatus (2), online (2), avoid (2), within (2), access (2), restarted (2), unexpectedly (2), compute (2), automatically (2), continue (2), slower (2), than (2), usual (2), recovered (2), errors (2), safe (2), html (2), valid (2), deployment (2), upgrade (2), something, went, wrong, try, again, thanks, subscribing, get, notifications, about, reported, 13th, august, websites, apologies, partner, logging, function, engineering, updating, particular, short, ssl, blocking, 05th, april, both, malfunction, send, notification, notified, earliest, seamlessly, west, affects, engineers, metadata, drop, overall, networking, manifesting, attempting, connect, wan, additionally, determine, flagged, thorough, concluded, fact, genuine, feel, free, invaluable, work, tuesday, restore, overwhelming, consequently, synchronization, secondary, new, failure, widget, display, sections, docs, remained, unaffected, responded, initiating, available, premium, transitioned, healthy, restoration, ultimately, deeply, regret, committed, occurrences, knowlege, friday, select, functionality, unusual, directed, towards, overwhelmed, partial, manager, hosting, includes, strengthening, better, handle, demands, challenges, diligently, only, resilient, but, efficient, responding, varying, upon, found, significant, marked, number, notable, directly, coupled, inability, establish, immediate, heal, setup, efficiently, reactive, could, adapt, severity, accessibility, aim, implement, proactive, responsiveness, ensuring, robust, unexpected, offline, attributing, meticulous, indeed, findings, affirm, throughout, authentic, sincerely, erroneous, pertaining, don, great, value, strive, continually, 02pm, substantial, reaching, maximum, concurrent, defined, start, details, made, code, faced, scheduled, limited, tags, received, alarm, endpoint, components, entering, addressed, through, changes, targeted, fixes, abnormal, fail, apps, seem, upgrades, temporarily, force, performing, forced, edge, cases, involving, constraints, bring, post, low, malicious, payloads, evaded, detection, existing, dos, layers, threat, actor, exploited, gaps, rule, sensitivity, bypassing, anomaly, scoring, involved, reinforcing, heuristics, adaptive, limiting, where, displayed, though, they, remain, acknowledge, most, face, occasional, steadily, 8gmgl950y3h7, confirmed, without, hence, cdn, noticed, brought, statement, starting, failures, trying, teams, management, workflow, deployed, blocked, subset, storage, clusters, restarting, lost, disks, applying, see, signs, applies, across, events, warrant, specific, pattern, caching, slowdown, keeping, close, watch, sure, stays, smoothly, brief, slow, delays, window, normalized, validated, recently, isolated, strictly, outs, pressure, prepared, traced, guardrails, unsafe, prevented, those, updated, validation, logic, allow, maintaining, intended, security, protections, completed, exceptions, reboot, responses, changed, primary, quick, succession, transitions, unable, obtain, repeatedly, extended, revisited, ceiling, headroom, inicdent, upstream, p95, p99, round, trip, saturation, surfacing, downstream, exceeded, client, thresholds, workload, side, end, contributed, remediated, fault, pools, error, around, silent, non, disruptive, refreshed,
Text of the page (random words):
in kb and apihub all applications are functioning as expected now show history investigating mar 18 2025 12 20 gmt 00 00 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 knowledge base operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime portal operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime portal api operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime api hub operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime user authentication operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime us operational knowledge base us operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime portal us operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime portal api us operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime api hub us operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime user authentication us operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime canada operational api hub operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime knowledge base operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime portal operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime portal api operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime user authentication operational nov 09 2026 uptime 100 000 nov 10 2026 uptime 100 000 nov 11 2026 uptime 100 000 nov 12 2026 uptime 100 000 nov 13 2026 uptime 100 000 nov 14 2026 uptime 100 000 nov 15 2026 uptime 100 000 uptime over the past 7 days 100 000 uptime monitor services in eu environment monitor document360 knowledge base monitor document360 portal monitor document360 portal api monitor document360 api hub monitors the user authentication in europe environment monitor servers in us environment monitors the knowledge base in us environment monitors the portal in us environment monitors the portal api in us environment monitors the api hub in us environment monitors the user authentication in us environment incidents intermittent slowness and timeouts in us environment resolved oct 06 2026 09 26 gmt 01 00 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 intermittent slowness and timeouts in eu environment resolved sep 30 2026 13 52 gmt 01 00 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 incident in canada environment resolved sep 28 2026 00 04 gmt 01 00 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 show history open sep 27 2026 23 39 gmt 01 00 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 intermittent slowness and timeouts in eu environment resolved sep 17 2026 11 17 gmt 01 00 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 we are experiencing slowness in eu environment kb site closed sep 10 2026 06 35 gmt 01 00 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 show history monitoring sep 08 2026 23 31 gmt 01 00 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 investigating sep 08 2026 22 49 gmt 01 00 we are experiencing an incident in eu environment in kb site we are currently investigating the inicdent slowness and timeouts in us environment resolved sep 09 2026 16 30 gmt 01 00 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 show history monitoring sep 09 2026 14 35 gmt 01 00 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 open sep 09 2026 14 24 gmt 01 00 we have observed spike exceptions in us environment for all application we are investigating this issue kb site rendering issue closed jul 13 2026 07 57 gmt 01 00 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 show history resolution in progress jul 13 2026 07 22 gmt 01 00 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 timeouts in eu environment resolved jun 23 2026 16 20 gmt 01 00 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 time outs in eu environment resolved may 18 2026 06 31 gmt 01 00 the issue has been resolved show history investigating may 18 2026 06 30 gmt 01 00 the issue has been resolved investigating apr 23 2026 19 35 gmt 01 00 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 eu knowledge base site slowness resolved apr 16 2026 06 11 gmt 01 00 the systems are now operational and the issue is now resolved show history monitoring apr 01 2026 15 26 gmt 01 00 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 eu application slowness and timeout resolved apr 16 2026 06 11 gmt 01 00 the systems are now operational and the issue is now resolved show history monitoring mar 29 2026 04 32 gmt 01 00 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 identified mar 29 2026 04 25 gmt 01 00 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 knowledge base site slowness closed mar 05 2026 23 20 gmt 00 00 the issue was caused due to high volume of requests in specific pattern we have taken measures to mitigate this in future service disruption in us environment closed feb 24 2026 12 50 gmt 00 00 services are stable now and closing this issue will continue to monitor the application health show history monitoring jul 19 2024 04 16 gmt 01 00 we have worked with azure and brought our services back online we are currently monitoring the situation status from azure https azure status microsoft en in status impact statement starting at 21 56 utc on 18 jul 2024 you have been identified as a customer using virtual machines in central us who may experience connection failures when trying to access some virtual machines hosted in the region these virtual machines may have also restarted unexpectedly current status we are aware of this issue and have engaged multiple teams we have determined the underlying cause a backend cluster management workflow deployed a configuration change causing backend access to be blocked between a subset of azure storage clusters and compute resources in the central us region this resulted in the compute resources automatically restarting when connectivity was lost to virtual disks we are currently applying mitigation customers should see signs of recovery at this time as mitigation applies across resources in the region the next update will be provided in 60 minutes or as events warrant open jul 19 2024 00 25 gmt 01 00 we are currently facing downtime in the portal and user authentication applications within our us environment caused by a disruption in azure services in the central us region our team is actively investigating this issue high response time for kb sites in eu environment closed feb 24 2026 00 00 gmt 00 00 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 show history investigating feb 17 2026 10 11 gmt 00 00 we have noticed an incident in eu knowledge base site the service has been stabilized now we are currently investigating the issue cdn issue resolved nov 18 2025 21 00 gmt 00 00 cloudflare has confirmed the issue has resolved and all our services have been working without any issue hence closing this issue show history monitoring nov 18 2025 12 55 gmt 00 00 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 open nov 18 2025 11 54 gmt 00 00 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 open nov 18 2025 11 46 gmt 00 00 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 slowness in eu environment resolved nov 03 2025 11 30 gmt 00 00 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 sensitivi...
|
