Public summaries / Private technical evidence
Network observations.
Evidence in context.
The latest 14 days of latency investigations from Stealth NYC to public AI endpoints. Trace comparisons and interface checks show what the evidence supports, and what remains open.
The measurement point32 Avenue of the Americas.Measured from Stealth’s New York City network.
- Document status
- Published
- Observation window
- 14 days
- Measurement point
- Stealth NYC
- Evidence scope
- Public summary
Published record. Updates run automatically.
What was observed.
What remains open.
Select an RCA for its evidence. Anomalies and possible SLA events remain separate flags.
Last evidence . View coverage and limits below
| Reference / Public endpoint | Observation interval | Trigger | Investigation state | Assessment |
|---|---|---|---|---|
| RCA-5BFA8CC77292D67AMistral · APIapi.mistral.ai | Last observed | Latency anomaly | Investigating | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-65F3246F94E644CAMicrosoft · Chat websitecopilot.microsoft.com | Last observed | Latency anomaly | Investigating | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C525D73F94A3FCFCOpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Investigating | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-B2264FB2CFE59626Mistral · APIapi.mistral.ai | Last observed | Latency anomaly | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-90D3547235335AF4Microsoft · Chat websitecopilot.microsoft.com | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-E12620F60571F5C4OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-ACD110680DF88E94Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-68E6C20CC3748159Mistral · APIapi.mistral.ai | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-1702189B28D9E1BBPerplexity · APIapi.perplexity.ai | Last observed | Possible SLA event | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-FA03D21FFEC59E3DMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-F42FACE97F396A40Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-A56CA7EA007823CDMicrosoft · Chat websitecopilot.microsoft.com | Last observed | Latency anomaly | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-4EDDF7B65C6A244CMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-513F72E75CA6D13DMistral · APIapi.mistral.ai | Last observed | Latency anomaly | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-6DE330D7D5A06648OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-BBD27CBD4578B380Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-3C44227D4FC8DB53Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-533FA3DBFA910383OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-B37022E9D0930E0AMicrosoft · Chat websitecopilot.microsoft.com | Last observed | Latency anomaly | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-3B62E0BEC4C4F4D5Perplexity · APIapi.perplexity.ai | Last observed | Latency anomaly | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-D314E06154039AEAMicrosoft · Chat websitecopilot.microsoft.com | Last observed | Latency anomaly | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-038CF442520AA5CFMistral · APIapi.mistral.ai | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-19209B6E5588FDBAPerplexity · APIapi.perplexity.ai | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-70204E43299C3EC6Microsoft · Chat websitecopilot.microsoft.com | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-912092D840D6F34BMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-B0D2D2AE7C9C3E20Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1619C72C29714DDFPerplexity · APIapi.perplexity.ai | Last observed | Possible SLA event | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-1C4EF84FDD5E8856Microsoft · Chat websitecopilot.microsoft.com | Last observed | Latency anomaly | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-3EE249A45D0997C0Perplexity · APIapi.perplexity.ai | Last observed | Latency anomaly | Recovered | Findings differ by destinationSuspected area: Findings differ by destinationLimited confidence |
| RCA-974264A5D61A534BOpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-50F4A73665218B1AMicrosoft · Chat websitecopilot.microsoft.com | Last observed | Possible SLA event | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-AF9DC7FC88E54DA3Perplexity · APIapi.perplexity.ai | Last observed | Latency anomaly | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-10AA4D45E13972DFMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C415045E5C4EC747Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-711FAFC7340DF342OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Stealth replies stable; external replies variedSuspected area: External path, destination or return pathLimited confidence |
| RCA-DE30BD4E1580D3FFOpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-21475E8F94B97590Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-E62D5CC0041A679BOpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-409BC33AF1B07A5BOpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-8DD916BDBAD93E55Microsoft · Chat websitecopilot.microsoft.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-CAA5C3B507B47584Microsoft · Chat websitecopilot.microsoft.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-00767AEBA9195947OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-91C8CC56929A1D11Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C85EB73DFB04C7E7xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-AD89B23B1313BC99xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-D6640D50361A9663Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-71C0214C63436820Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-5A93CE3920D094FFMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-E3F5833E2472DC68Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-2FCE57EB507DE663Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-2CC4F9EA9BFA7AC4OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C84309AB6977AD64OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-50D41631F092BDE9xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-AA2CAF439193DA71Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-F24220332B46CE09OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1C120F2AED92D3EEMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-A31F0BB24106FB1COpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-BC6A359E02F8AC89OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-82343BF903FC8B61xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1962E9B74A4EE9D8Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-F658BB5180786AF4Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-003102F655F81D22OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-099B6D2033C198F8OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-40AAC4F3C122EC68xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1FBA9A992FB92F0EMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-2C89AD7DE7A02CE2xAI · APIapi.x.ai | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-0A72836449A8A0C0xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-E90B6E47F262EFA6Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-0193914E94F62D84Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-7D031C9A1A77622AMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-863092DF6C20B240Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-30B14E488C713C6AMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-BB493A74CA71BAACPerplexity · APIapi.perplexity.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-8361C06FE3C66213Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1F3B283BA2CAF855OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-7ABC95D8CC47CDBAMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1E47E11E7CEC9832OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-27B2D6295C06912BMistral · APIapi.mistral.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-EC2BB5F62A4A1CBEOpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-386E71A17870EB63OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-E81DC6C5F31854FBOpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-390E95AFBF636216Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-2A5BEC9280BB9C1DxAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-A22BC0ECBE93A8BDOpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-99AB5A1E84B2478CMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C123A93EF39999B1OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-D72E9A8DD4636684OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-FC15460789A9E5F3OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-19B14EC9A0BF0DFFOpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-BBC0CC412A3FBDE1OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-CF7D9BF3BAF9C600OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-798EEFA4FE6F7225OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1CA18BBB2B33B0F0xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-3D0BDBE055B58332Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-FC49A3A67C784125xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-5279098EEB71F611Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-8AF499244A029279xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-F2B06CA95FAD2C82Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-56C353E0F1E95F19Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-A084C78F7F46AD1AMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-465AB16D45A13567Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1AEA4E6ED32AFDBCMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-12CC6E6040F73F88OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-93605DCFA59F7D1BOpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-A96CF264CC56AAC9OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C817EB7A5089E908OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-6E73EAF655856774OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C6E4970CAE98A615OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-213CDFCECAA0E728xAI · APIapi.x.ai | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-FFA688EFF870F3BFOpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-4542582C026E178DOpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-AFF763EB38C8C936OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-FF2729E4706C14D7OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-D2CE306262CD0873OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-5317A835DBB75261OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-8ACF2C656F952C93OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-D0456AEE723E28F4OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-9BCDA79614C5D058OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-2107DB9874897DFEOpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-06CE3D98DC2A99F7Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-15BBCA62E6718CEFOpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-C250E0677CC13737Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-30F5B2D8283A0988Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-4D3B6AA54200DC1FOpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-820A68EDB74E9550Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-7B092812D460601DMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-657FBD54AE46C631OpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-9877851923AE07E0OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-094EAB3FCA6D3566Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-F1136B7565C7A1ACOpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-663F3DD00948AFE9OpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-1A456569BC0FA69EOpenAI · APIapi.openai.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-66F2F25FBB08F23FOpenAI · Chat websitechatgpt.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-D3FADB4614F4EBC3OpenAI · APIapi.openai.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-E645E3F3D18C2163xAI · APIapi.x.ai | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-54FFB52D70BDD7A9Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-461389D567704146xAI · APIapi.x.ai | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-CDAC4AE924EEAF4AMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-9B998344B43DCB7BMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-8422F38C8F31B70DMicrosoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-6818366A81155897OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-CD45A5E347B6ED71OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-A4BC72AF2AD679B0Microsoft · Chat websitecopilot.com | Last observed | Possible SLA event | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
| RCA-3A04372189F58972OpenAI · Chat websitechatgpt.com | Last observed | Latency anomaly | Recovered | Cause unresolvedSuspected area: Not localizedInsufficient evidence |
Investigation summaries and measurements
Mistralapi.mistral.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Baseline RTT
- 1.318 ms
- Event RTT
- 1.209 ms
- Event p95
- 5.673 ms
- Successful / expected recordings
- 40 / 40
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Analysis pending.
Unresolved conditions
- Historical trace comparison is pending.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Baseline RTT
- 1.089 ms
- Event RTT
- 1.364 ms
- Event p95
- 10.368 ms
- Successful / expected recordings
- 40 / 40
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Analysis pending.
Unresolved conditions
- Historical trace comparison is pending.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Baseline RTT
- 1.564 ms
- Event RTT
- 1.573 ms
- Event p95
- 7.258 ms
- Successful / expected recordings
- 50 / 50
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Analysis pending.
Unresolved conditions
- Historical trace comparison is pending.
Mistralapi.mistral.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.317 ms
- Event RTT
- 1.193 ms
- Event p95
- 5.506 ms
- Successful / expected recordings
- 119 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.076 ms
- Event RTT
- 1.405 ms
- Event p95
- 17.869 ms
- Successful / expected recordings
- 586 / 610
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.549 ms
- Event RTT
- 1.145 ms
- Event p95
- 17.638 ms
- Successful / expected recordings
- 705 / 730
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.713 ms
- Event RTT
- 6.080 ms
- Event p95
- 22.920 ms
- Successful / expected recordings
- 139 / 140
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Mistralapi.mistral.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.308 ms
- Event RTT
- 1.405 ms
- Event p95
- 17.436 ms
- Successful / expected recordings
- 536 / 560
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Perplexityapi.perplexity.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.272 ms
- Event RTT
- 1.370 ms
- Event p95
- 17.355 ms
- Successful / expected recordings
- 695 / 720
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.719 ms
- Event RTT
- 6.379 ms
- Event p95
- 18.015 ms
- Successful / expected recordings
- 130 / 130
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.720 ms
- Event RTT
- 6.101 ms
- Event p95
- 17.707 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.071 ms
- Event RTT
- 1.540 ms
- Event p95
- 13.777 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.733 ms
- Event RTT
- 6.736 ms
- Event p95
- 26.816 ms
- Successful / expected recordings
- 140 / 140
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Mistralapi.mistral.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.348 ms
- Event RTT
- 1.862 ms
- Event p95
- 3.600 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.353 ms
- Event RTT
- 1.580 ms
- Event p95
- 2.049 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.740 ms
- Event RTT
- 6.384 ms
- Event p95
- 22.901 ms
- Successful / expected recordings
- 160 / 160
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.738 ms
- Event RTT
- 6.421 ms
- Event p95
- 17.743 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.358 ms
- Event RTT
- 1.201 ms
- Event p95
- 15.719 ms
- Successful / expected recordings
- 667 / 670
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.227 ms
- Event RTT
- 1.055 ms
- Event p95
- 9.717 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Perplexityapi.perplexity.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.282 ms
- Event RTT
- 1.165 ms
- Event p95
- 8.779 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.165 ms
- Event RTT
- 1.359 ms
- Event p95
- 7.467 ms
- Successful / expected recordings
- 80 / 80
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Mistralapi.mistral.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.405 ms
- Event RTT
- 1.394 ms
- Event p95
- 16.671 ms
- Successful / expected recordings
- 579 / 580
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Perplexityapi.perplexity.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.278 ms
- Event RTT
- 1.329 ms
- Event p95
- 18.553 ms
- Successful / expected recordings
- 216 / 220
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.123 ms
- Event RTT
- 1.374 ms
- Event p95
- 17.678 ms
- Successful / expected recordings
- 238 / 240
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.735 ms
- Event RTT
- 6.737 ms
- Event p95
- 22.951 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.729 ms
- Event RTT
- 6.730 ms
- Event p95
- 22.904 ms
- Successful / expected recordings
- 250 / 250
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Perplexityapi.perplexity.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.276 ms
- Event RTT
- 1.124 ms
- Event p95
- 16.460 ms
- Successful / expected recordings
- 70 / 70
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.101 ms
- Event RTT
- 1.349 ms
- Event p95
- 13.963 ms
- Successful / expected recordings
- 210 / 210
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Perplexityapi.perplexity.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.272 ms
- Event RTT
- 1.328 ms
- Event p95
- 11.207 ms
- Successful / expected recordings
- 229 / 230
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Findings differ by destination. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaFindings differ by destination
Findings differ between destination comparisons. The evidence does not point to one location for the whole event.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.360 ms
- Event RTT
- 1.163 ms
- Event p95
- 11.294 ms
- Successful / expected recordings
- 219 / 220
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.096 ms
- Event RTT
- 3.502 ms
- Event p95
- 14.164 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Perplexityapi.perplexity.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.267 ms
- Event RTT
- 1.317 ms
- Event p95
- 13.262 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.747 ms
- Event RTT
- 6.949 ms
- Event p95
- 22.910 ms
- Successful / expected recordings
- 140 / 140
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.742 ms
- Event RTT
- 6.626 ms
- Event p95
- 22.896 ms
- Successful / expected recordings
- 150 / 150
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.363 ms
- Event RTT
- 1.130 ms
- Event p95
- 1.809 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Stealth replies stable; external replies varied. Limited confidence. Findings do not assign contractual responsibility.
Suspected areaExternal path, destination or return path
Sampled Stealth associated replies stayed within the comparison limits while external replies varied. The external path, destination and return path remain areas to investigate.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.366 ms
- Event RTT
- 1.181 ms
- Event p95
- 17.286 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.749 ms
- Event RTT
- 5.987 ms
- Event p95
- 22.895 ms
- Successful / expected recordings
- 248 / 250
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
The available comparison does not show which part of the network explains the increase.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.369 ms
- Event RTT
- 1.152 ms
- Event p95
- 7.875 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.369 ms
- Event RTT
- 1.428 ms
- Event p95
- 19.137 ms
- Successful / expected recordings
- 1103 / 1120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.080 ms
- Event RTT
- 1.021 ms
- Event p95
- 9.791 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.microsoft.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.085 ms
- Event RTT
- 0.993 ms
- Event p95
- 17.802 ms
- Successful / expected recordings
- 758 / 770
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.374 ms
- Event RTT
- 1.358 ms
- Event p95
- 18.231 ms
- Successful / expected recordings
- 860 / 870
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.766 ms
- Event RTT
- 6.650 ms
- Event p95
- 23.053 ms
- Successful / expected recordings
- 170 / 170
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.354 ms
- Event RTT
- 1.443 ms
- Event p95
- 4.185 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.354 ms
- Event RTT
- 1.354 ms
- Event p95
- 7.578 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.765 ms
- Event RTT
- 6.414 ms
- Event p95
- 22.897 ms
- Successful / expected recordings
- 150 / 150
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.760 ms
- Event RTT
- 6.743 ms
- Event p95
- 22.889 ms
- Successful / expected recordings
- 89 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.746 ms
- Event RTT
- 6.519 ms
- Event p95
- 22.905 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.734 ms
- Event RTT
- 6.907 ms
- Event p95
- 22.929 ms
- Successful / expected recordings
- 370 / 370
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.759 ms
- Event RTT
- 6.645 ms
- Event p95
- 22.914 ms
- Successful / expected recordings
- 190 / 190
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.357 ms
- Event RTT
- 1.363 ms
- Event p95
- 19.700 ms
- Successful / expected recordings
- 330 / 330
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.370 ms
- Event RTT
- 1.349 ms
- Event p95
- 19.818 ms
- Successful / expected recordings
- 130 / 130
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Repeated replies from a comparable hop showed increased round trip time.
- Baseline RTT
- 1.358 ms
- Event RTT
- 1.402 ms
- Event p95
- 7.579 ms
- Successful / expected recordings
- 140 / 140
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.755 ms
- Event RTT
- 6.393 ms
- Event p95
- 22.919 ms
- Successful / expected recordings
- 140 / 140
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.371 ms
- Event RTT
- 1.459 ms
- Event p95
- 5.477 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.741 ms
- Event RTT
- 6.739 ms
- Event p95
- 22.904 ms
- Successful / expected recordings
- 150 / 150
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.356 ms
- Event RTT
- 1.163 ms
- Event p95
- 18.858 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.370 ms
- Event RTT
- 1.470 ms
- Event p95
- 13.914 ms
- Successful / expected recordings
- 100 / 100
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.357 ms
- Event RTT
- 1.319 ms
- Event p95
- 5.442 ms
- Successful / expected recordings
- 70 / 70
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.737 ms
- Event RTT
- 6.416 ms
- Event p95
- 22.864 ms
- Successful / expected recordings
- 140 / 140
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.723 ms
- Event RTT
- 6.802 ms
- Event p95
- 22.916 ms
- Successful / expected recordings
- 280 / 280
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.347 ms
- Event RTT
- 1.364 ms
- Event p95
- 19.685 ms
- Successful / expected recordings
- 936 / 960
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.367 ms
- Event RTT
- 1.339 ms
- Event p95
- 19.539 ms
- Successful / expected recordings
- 748 / 760
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.357 ms
- Event RTT
- 1.399 ms
- Event p95
- 5.292 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.719 ms
- Event RTT
- 6.268 ms
- Event p95
- 22.915 ms
- Successful / expected recordings
- 80 / 80
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.355 ms
- Event RTT
- 1.358 ms
- Event p95
- 10.985 ms
- Successful / expected recordings
- 180 / 180
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.355 ms
- Event RTT
- 1.414 ms
- Event p95
- 7.665 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.691 ms
- Event RTT
- 6.737 ms
- Event p95
- 22.908 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.697 ms
- Event RTT
- 6.711 ms
- Event p95
- 22.923 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.674 ms
- Event RTT
- 6.292 ms
- Event p95
- 22.906 ms
- Successful / expected recordings
- 320 / 320
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.674 ms
- Event RTT
- 6.858 ms
- Event p95
- 27.612 ms
- Successful / expected recordings
- 180 / 180
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.676 ms
- Event RTT
- 6.879 ms
- Event p95
- 27.617 ms
- Successful / expected recordings
- 120 / 120
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Perplexityapi.perplexity.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.278 ms
- Event RTT
- 1.283 ms
- Event p95
- 3.392 ms
- Successful / expected recordings
- 474 / 500
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.696 ms
- Event RTT
- 6.139 ms
- Event p95
- 22.870 ms
- Successful / expected recordings
- 69 / 70
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.346 ms
- Event RTT
- 1.414 ms
- Event p95
- 3.119 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.715 ms
- Event RTT
- 6.502 ms
- Event p95
- 22.868 ms
- Successful / expected recordings
- 80 / 80
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.348 ms
- Event RTT
- 1.170 ms
- Event p95
- 17.556 ms
- Successful / expected recordings
- 1172 / 1180
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Mistralapi.mistral.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.637 ms
- Event RTT
- 1.702 ms
- Event p95
- 3.824 ms
- Successful / expected recordings
- 326 / 350
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.366 ms
- Event RTT
- 1.411 ms
- Event p95
- 9.002 ms
- Successful / expected recordings
- 210 / 210
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.367 ms
- Event RTT
- 1.333 ms
- Event p95
- 16.498 ms
- Successful / expected recordings
- 369 / 370
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.367 ms
- Event RTT
- 1.398 ms
- Event p95
- 17.621 ms
- Successful / expected recordings
- 219 / 220
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.728 ms
- Event RTT
- 6.256 ms
- Event p95
- 22.889 ms
- Successful / expected recordings
- 70 / 70
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.353 ms
- Event RTT
- 1.347 ms
- Event p95
- 4.826 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.348 ms
- Event RTT
- 1.457 ms
- Event p95
- 5.393 ms
- Successful / expected recordings
- 99 / 100
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.729 ms
- Event RTT
- 6.730 ms
- Event p95
- 22.918 ms
- Successful / expected recordings
- 870 / 870
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.345 ms
- Event RTT
- 1.116 ms
- Event p95
- 4.943 ms
- Successful / expected recordings
- 190 / 190
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.366 ms
- Event RTT
- 1.412 ms
- Event p95
- 4.962 ms
- Successful / expected recordings
- 80 / 80
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.344 ms
- Event RTT
- 1.355 ms
- Event p95
- 8.014 ms
- Successful / expected recordings
- 70 / 70
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.365 ms
- Event RTT
- 1.338 ms
- Event p95
- 5.817 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.343 ms
- Event RTT
- 1.215 ms
- Event p95
- 9.040 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.358 ms
- Event RTT
- 1.315 ms
- Event p95
- 17.933 ms
- Successful / expected recordings
- 834 / 840
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.324 ms
- Event RTT
- 1.204 ms
- Event p95
- 19.268 ms
- Successful / expected recordings
- 826 / 840
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.350 ms
- Event RTT
- 1.419 ms
- Event p95
- 9.053 ms
- Successful / expected recordings
- 130 / 130
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.722 ms
- Event RTT
- 6.742 ms
- Event p95
- 22.947 ms
- Successful / expected recordings
- 130 / 130
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.349 ms
- Event RTT
- 1.359 ms
- Event p95
- 5.213 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.703 ms
- Event RTT
- 6.742 ms
- Event p95
- 22.901 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Repeated replies from a comparable hop showed increased round trip time.
- Baseline RTT
- 1.346 ms
- Event RTT
- 1.468 ms
- Event p95
- 11.613 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.681 ms
- Event RTT
- 6.524 ms
- Event p95
- 22.915 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.543 ms
- Event RTT
- 6.248 ms
- Event p95
- 22.912 ms
- Successful / expected recordings
- 570 / 570
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.532 ms
- Event RTT
- 6.549 ms
- Event p95
- 22.890 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.522 ms
- Event RTT
- 6.289 ms
- Event p95
- 22.942 ms
- Successful / expected recordings
- 190 / 190
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Historical traces compared. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.517 ms
- Event RTT
- 6.510 ms
- Event p95
- 22.896 ms
- Successful / expected recordings
- 160 / 160
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.378 ms
- Event RTT
- 1.744 ms
- Event p95
- 17.109 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.361 ms
- Event RTT
- 2.803 ms
- Event p95
- 15.226 ms
- Successful / expected recordings
- 529 / 530
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.378 ms
- Event RTT
- 1.354 ms
- Event p95
- 10.942 ms
- Successful / expected recordings
- 130 / 130
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.380 ms
- Event RTT
- 1.347 ms
- Event p95
- 9.699 ms
- Successful / expected recordings
- 129 / 130
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.382 ms
- Event RTT
- 1.172 ms
- Event p95
- 16.818 ms
- Successful / expected recordings
- 975 / 980
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.385 ms
- Event RTT
- 1.433 ms
- Event p95
- 14.156 ms
- Successful / expected recordings
- 289 / 290
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Baseline RTT
- 1.390 ms
- Event RTT
- 1.492 ms
- Event p95
- 11.226 ms
- Successful / expected recordings
- 100 / 100
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.386 ms
- Event RTT
- 2.064 ms
- Event p95
- 18.919 ms
- Successful / expected recordings
- 70 / 70
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.387 ms
- Event RTT
- 1.370 ms
- Event p95
- 13.065 ms
- Successful / expected recordings
- 170 / 170
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.389 ms
- Event RTT
- 1.336 ms
- Event p95
- 15.664 ms
- Successful / expected recordings
- 210 / 210
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.373 ms
- Event RTT
- 1.388 ms
- Event p95
- 2.013 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.373 ms
- Event RTT
- 1.367 ms
- Event p95
- 9.893 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.387 ms
- Event RTT
- 1.660 ms
- Event p95
- 6.246 ms
- Successful / expected recordings
- 100 / 100
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.374 ms
- Event RTT
- 1.490 ms
- Event p95
- 10.906 ms
- Successful / expected recordings
- 220 / 220
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.375 ms
- Event RTT
- 1.404 ms
- Event p95
- 14.759 ms
- Successful / expected recordings
- 100 / 100
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.378 ms
- Event RTT
- 1.458 ms
- Event p95
- 18.752 ms
- Successful / expected recordings
- 944 / 1080
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.388 ms
- Event RTT
- 1.407 ms
- Event p95
- 12.566 ms
- Successful / expected recordings
- 189 / 190
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.704 ms
- Event RTT
- 6.783 ms
- Event p95
- 22.966 ms
- Successful / expected recordings
- 100 / 100
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.388 ms
- Event RTT
- 1.404 ms
- Event p95
- 17.231 ms
- Successful / expected recordings
- 507 / 510
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.717 ms
- Event RTT
- 6.420 ms
- Event p95
- 18.340 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.696 ms
- Event RTT
- 6.848 ms
- Event p95
- 18.341 ms
- Successful / expected recordings
- 170 / 170
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.387 ms
- Event RTT
- 1.564 ms
- Event p95
- 6.088 ms
- Successful / expected recordings
- 90 / 90
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.718 ms
- Event RTT
- 6.429 ms
- Event p95
- 22.963 ms
- Successful / expected recordings
- 170 / 170
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.704 ms
- Event RTT
- 6.733 ms
- Event p95
- 22.950 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.372 ms
- Event RTT
- 1.199 ms
- Event p95
- 16.552 ms
- Successful / expected recordings
- 310 / 310
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.384 ms
- Event RTT
- 1.499 ms
- Event p95
- 8.678 ms
- Successful / expected recordings
- 210 / 210
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.718 ms
- Event RTT
- 6.341 ms
- Event p95
- 22.987 ms
- Successful / expected recordings
- 150 / 150
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.371 ms
- Event RTT
- 1.380 ms
- Event p95
- 8.202 ms
- Successful / expected recordings
- 80 / 80
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.383 ms
- Event RTT
- 1.362 ms
- Event p95
- 6.030 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.381 ms
- Event RTT
- 1.367 ms
- Event p95
- 12.207 ms
- Successful / expected recordings
- 280 / 280
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.361 ms
- Event RTT
- 1.374 ms
- Event p95
- 19.367 ms
- Successful / expected recordings
- 1082 / 1100
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIapi.openai.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.375 ms
- Event RTT
- 1.346 ms
- Event p95
- 19.492 ms
- Successful / expected recordings
- 646 / 650
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Baseline RTT
- 1.378 ms
- Event RTT
- 1.356 ms
- Event p95
- 9.097 ms
- Successful / expected recordings
- 250 / 250
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.715 ms
- Event RTT
- 6.415 ms
- Event p95
- 22.940 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
xAIapi.x.ai
Observed facts
- A sustained increase in measured round trip time was observed.
- Baseline RTT
- 1.377 ms
- Event RTT
- 1.379 ms
- Event p95
- 11.874 ms
- Successful / expected recordings
- 110 / 110
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.708 ms
- Event RTT
- 6.659 ms
- Event p95
- 22.990 ms
- Successful / expected recordings
- 180 / 180
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.709 ms
- Event RTT
- 6.730 ms
- Event p95
- 22.957 ms
- Successful / expected recordings
- 70 / 70
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.672 ms
- Event RTT
- 6.743 ms
- Event p95
- 22.960 ms
- Successful / expected recordings
- 240 / 240
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.351 ms
- Event RTT
- 1.476 ms
- Event p95
- 2.057 ms
- Successful / expected recordings
- 60 / 60
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.351 ms
- Event RTT
- 1.380 ms
- Event p95
- 8.416 ms
- Successful / expected recordings
- 230 / 230
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
Microsoftcopilot.com
Observed facts
- A sustained increase in measured round trip time was observed.
- The measured destination address changed across the comparison period.
- Baseline RTT
- 6.556 ms
- Event RTT
- 6.743 ms
- Event p95
- 22.953 ms
- Successful / expected recordings
- 160 / 160
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparable history unavailable. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
OpenAIchatgpt.com
Observed facts
- A sustained increase in measured round trip time was observed.
- Stored traces were compared using matching source and destination addresses.
- Baseline RTT
- 1.351 ms
- Event RTT
- 1.204 ms
- Event p95
- 5.223 ms
- Successful / expected recordings
- 80 / 80
Successful recordings are not an uptime percentage. p95 describes the upper end of successful RTT recordings in the event evidence.
Assessment
Cause unresolved. Insufficient evidence. Findings do not assign contractual responsibility.
Suspected areaNot localized
A usable before and during path comparison is unavailable. The event cannot be localized from this evidence.
Comparison incomplete. Assessed UTC.
Recovery observed UTC.
Unresolved conditions
- Comparable historical traces are missing or insufficient.
- The traces do not establish that probes used an identical packet flow.
- The return path has not been independently verified.
- A complete path-specific router assessment is unavailable for this historical interval.
- A supported path assessment has not yet been published for this investigation.
The record.
And its limits.
Current collection health. Missing evidence remains unknown.
Native router timestamps are verified for the candidate path readings evaluated in this snapshot.
Publication and collection timestamps
Public snapshot published UTC · 10 seconds ago. Collection began UTC. Page refresh times are separate from measurement timestamps.
An observation.
Then an assessment.
Findings are bounded by what the measurements can establish. Uncertainty remains visible.
- 01EndpointThe address actually measured
- 02ForwardingThe route observed at that time
- 03InterfacesState, traffic and counter changes
- 04OpticsReadings and reported thresholds
- 05AssessmentCorroboration, gaps and limits
Findings describe sampled observations. Exact packet paths, hidden queues and the return path remain uncertain. Confidence is qualitative, not a probability of cause.
What the evidence describes
Path and interface evidence
IPv4 measurements originate from Stealth NYC. Hostnames may resolve to CDN or shared service edges. ICMP traces use echo probes. TCP/443 traces send SYN probes to TCP port 443 only; they do not complete a TCP handshake or perform a TLS or HTTP exchange. Neither measures application or model response time.
Historical comparison runs for every investigation. Stored traces before and during the event are compared for matching destinations. Mapped interface evidence is assessed for the compared interval; missing historical readings remain unavailable.
Stable Stealth replies and interface observations without corresponding errors or sustained capacity pressure reduce the likelihood of a Stealth forwarding issue. Normal optics alone do not rule out congestion.
Limits of localization
The Stealth gNMI interface verifies the active route-table choice and maps its primary next hop to the Stealth logical interface, configured attachment and, where applicable, the known LAG member set at each snapshot. Stealth does not use ECMP in this monitored scope. The snapshot does not identify which physical LAG member carried a particular independent probe, attest line-card forwarding at that packet instant, prove the exact application packet flow or observe the return path. LAG load balancing, tunnels, silent routers and asymmetric return paths can hide the path taken by a particular packet. No remote reverse traceroute is available.
Slow intermediate ICMP replies may reflect reply handling rather than slow forwarding. Destination changes, reply coverage and delay persisting through later hops are considered separately. Address registration identifies the recorded holder, not fault responsibility.
A destination that does not respond to a trace may be filtering probes or handling replies differently. Trace nonresponse alone does not establish an endpoint outage.
Public summaries cover 14 days; private technical evidence is retained for 365 days. Reply coverage percentages count comparable replies, not the probability of a cause.
Anomalies, possible SLA events and confidence
Operational anomaly rule
Three consecutive completed five minute intervals must each contain at least nine of ten expected successful recordings. Each interval’s p95 must exceed both twice the baseline and the baseline plus 2 ms.
The baseline is the median of at least 120 underlying recordings in the preceding 24 hours, excluding the latest 15 minutes. Statistics use successful recordings, not chart averages.
What the labels mean
An anomaly is a sustained latency change. A possible SLA event is a separate flag. Neither establishes an application outage, an attributable breach or customer eligibility.
ICMP non-response alone does not establish an outage. Confidence labels express the strength and limits of the evidence; they are not calibrated probabilities. The signed agreement governs SLA eligibility, attribution and remedies.
Read the AI connectivity SLAHow load is assessed
Ingress and egress are assessed separately on mapped physical candidate links, including individual LAG members. An 80% warning requires three consecutive completed five minute intervals, each with at least 90% valid time coverage and nine valid counter intervals. Recovery requires two qualified intervals below 70%.
Capacity, counter precision, reset evidence and link changes are checked first. Missing evidence remains unknown. The warning does not establish congestion; lower interval averages can conceal microbursts or queue pressure.
References: Round trip delay and path asymmetry · Measurement uncertainty · ICMP reply limits.
A concern
about your connection?
Contact Stealth support with your circuit details, the destination and the time observed. The public investigation record does not replace a support notification.
Contact Stealth support