Damn, is it down?

All services / Outsystems / Nov 9, 2026 / Evidence

Evidence

Evidence: Outsystems, Nov 9, 2026

The raw data behind this incident page: every check we ran, the regions that failed, the error codes and the user report curve. Check our work.

Our verdict: Vendor-reported issue: only the company's status page flagged it; our checks and user reports did not confirm an outage. How we verify outages

Download JSON Download CSV Also at /api/v1/outages/1148/evidence. Free to reuse with attribution.

0 of 152Checks failed in the window
0 of 4Regions failing
—Most common error code
0Peak user reports in 15 min

Window: to . Checks from 15 minutes before the start to 15 minutes after recovery (or now). Report curve: one hour either side. Tables are in UTC.

Error codes

No failed checks with an error code in this window.

Passing checks with a note (counted as up, not as failures): bot_challenge ×8.

http_5xx = the site answered with that server error; timeout = no answer in time; network = the connection failed; origin_reset = the connection to the site's server was reset (HTTP 520–527) and a second fetch path got no answer either; no_status = no usable answer. Bot walls (bot_*), certificate problems on a server that answers (cert_*) and maintenance pages count as up.

Regions

  • We check from: US East, US West, Europe, Asia-Pacific.
  • Failing during this incident: none recorded.

Regional probes run from Cloudflare data centers in each region. We keep the latest regional result per region, plus a timestamped timeline entry when a region starts failing during an incident, so older incidents show the failing regions and when each was first seen, not every regional probe.

Report curve

No user reports for Outsystems in this window.

User reports per 15-minute bucket. Counts only: no reporter identity, IP address, location or text is published. We call reports a spike at 5 or more in 15 minutes.

Raw checks

152 checks, 0 failed.

All 152 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200319 ms—scheduled
Pass2004009 ms—scheduled
Pass2001853 ms—scheduled
Pass2001798 ms—scheduled
Pass2001611 ms—scheduled
Pass2001692 ms—scheduled
Pass2002021 ms—scheduled
Pass200278 ms—scheduled
Pass200320 ms—scheduled
Pass200289 ms—scheduled
Pass200317 ms—scheduled
Pass200324 ms—scheduled
Pass200255 ms—scheduled
Pass200362 ms—scheduled
Pass200284 ms—scheduled
Pass200245 ms—scheduled
Pass200258 ms—scheduled
Pass20261 msbot_challengescheduled
Pass200388 ms—scheduled
Pass200325 ms—scheduled
Pass200258 ms—scheduled
Pass200257 ms—scheduled
Pass200389 ms—scheduled
Pass200273 ms—scheduled
Pass200253 ms—scheduled
Pass200264 ms—scheduled
Pass200317 ms—scheduled
Pass200362 ms—scheduled
Pass200188 ms—scheduled
Pass200324 ms—scheduled
Pass200217 ms—scheduled
Pass200282 ms—scheduled
Pass200313 ms—scheduled
Pass200250 ms—scheduled
Pass200269 ms—scheduled
Pass200209 ms—scheduled
Pass200190 ms—scheduled
Pass200241 ms—scheduled
Pass200420 ms—scheduled
Pass20245 msbot_challengescheduled
Pass200252 ms—scheduled
Pass200214 ms—scheduled
Pass200264 ms—scheduled
Pass200235 ms—scheduled
Pass200222 ms—scheduled
Pass200219 ms—scheduled
Pass200254 ms—scheduled
Pass200343 ms—scheduled
Pass200266 ms—scheduled
Pass200243 ms—scheduled
Pass200262 ms—scheduled
Pass200246 ms—scheduled
Pass200288 ms—scheduled
Pass200240 ms—scheduled
Pass200358 ms—scheduled
Pass200367 ms—scheduled
Pass200281 ms—scheduled
Pass200266 ms—scheduled
Pass200370 ms—scheduled
Pass200245 ms—scheduled
Pass200288 ms—scheduled
Pass200209 ms—scheduled
Pass2001636 ms—scheduled
Pass200259 ms—scheduled
Pass200276 ms—scheduled
Pass200212 ms—scheduled
Pass200187 ms—scheduled
Pass200323 ms—scheduled
Pass200250 ms—scheduled
Pass200354 ms—scheduled
Pass200240 ms—scheduled
Pass200206 ms—scheduled
Pass200258 ms—scheduled
Pass200199 ms—scheduled
Pass200204 ms—scheduled
Pass200225 ms—scheduled
Pass200271 ms—scheduled
Pass200280 ms—scheduled
Pass200305 ms—scheduled
Pass20279 msbot_challengescheduled
Pass200318 ms—scheduled
Pass200297 ms—scheduled
Pass200340 ms—scheduled
Pass200265 ms—scheduled
Pass200221 ms—scheduled
Pass200315 ms—scheduled
Pass2003360 ms—scheduled
Pass200240 ms—scheduled
Pass200228 ms—scheduled
Pass200252 ms—scheduled
Pass200318 ms—scheduled
Pass200290 ms—scheduled
Pass200314 ms—scheduled
Pass200217 ms—scheduled
Pass20249 msbot_challengescheduled
Pass200232 ms—scheduled
Pass200331 ms—scheduled
Pass200216 ms—scheduled
Pass200173 ms—scheduled
Pass200202 ms—scheduled
Pass200172 ms—scheduled
Pass200227 ms—scheduled
Pass200314 ms—scheduled
Pass200197 ms—scheduled
Pass200217 ms—scheduled
Pass200216 ms—scheduled
Pass200231 ms—scheduled
Pass200213 ms—scheduled
Pass200203 ms—scheduled
Pass200221 ms—scheduled
Pass200314 ms—scheduled
Pass20288 msbot_challengescheduled
Pass200205 ms—scheduled
Pass200320 ms—scheduled
Pass200355 ms—scheduled
Pass200232 ms—scheduled
Pass200313 ms—scheduled
Pass200262 ms—scheduled
Pass200321 ms—scheduled
Pass200373 ms—scheduled
Pass200192 ms—scheduled
Pass200260 ms—scheduled
Pass200178 ms—scheduled
Pass200204 ms—scheduled
Pass200265 ms—scheduled
Pass200221 ms—scheduled
Pass200209 ms—scheduled
Pass200194 ms—scheduled
Pass200276 ms—scheduled
Pass200171 ms—scheduled
Pass200252 ms—scheduled
Pass200355 ms—scheduled
Pass200183 ms—scheduled
Pass200198 ms—scheduled
Pass200212 ms—scheduled
Pass200317 ms—scheduled
Pass200274 ms—scheduled
Pass200224 ms—scheduled
Pass20223 msbot_challengescheduled
Pass200222 ms—scheduled
Pass200194 ms—scheduled
Pass200367 ms—scheduled
Pass200202 ms—scheduled
Pass20247 msbot_challengescheduled
Pass200239 ms—scheduled
Pass200209 ms—scheduled
Pass20226 msbot_challengescheduled
Pass200169 ms—scheduled
Pass200221 ms—scheduled
Pass200207 ms—scheduled
Pass200206 ms—scheduled
Pass200360 ms—scheduled

Every main HTTP check of this service in the window, oldest first: the scheduled check time, when the probe actually ran, the result, HTTP status, latency and the stored error code. A failed check is a 5xx or 408 answer, a timeout or a failed connection; bot walls and maintenance pages count as passing and are noted in passing_notes.

How to check this

  • Compare checks.rows with the outage page: the first and last failed checks bound the incident times we published.
  • error_codes counts every failed check by its stored code; recount it from checks.rows.
  • report_curve.points sum to summary.reports_in_curve; the peak is summary.peak_reports_15m.
  • Disagree? Dispute it at https://damnisitdown.com/support?dispute=1148

No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.

← Back to the incident · Methodology · Dispute this report