Is Incident Notes Export Semantic Parity down?
Up
No, Incident Notes Export Semantic Parity is up.
It passed its latest check 2 h ago in 358 ms, and every check since we started checking it on 15 Oct 2026.
Latest check
- Last check
- 2 h ago (17 Oct 2026, 07:27 UTC)
- Response time
- 358 ms (typical 228 ms)
- Next check
- In about 2 h
- How often
- About every 5 hours over the last 7 days
Uptime
Uptime is the share of checks that passed. We checked it about every 5 hours over the last 7 days.
Outages in the last 30 days
No outages in the last 30 days. An outage starts when two checks in a row fail and ends at the next passing check.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 17 Oct 2026, 07:27 UTC | Passed | 402 | 358 ms |
| 17 Oct 2026, 02:41 UTC | Passed | 402 | 213 ms |
| 16 Oct 2026, 21:54 UTC | Passed | 402 | 266 ms |
| 16 Oct 2026, 17:10 UTC | Passed | 402 | 233 ms |
| 16 Oct 2026, 12:27 UTC | Passed | 402 | 266 ms |
| 16 Oct 2026, 07:50 UTC | Passed | 402 | 201 ms |
| 16 Oct 2026, 03:15 UTC | Passed | 402 | 213 ms |
| 15 Oct 2026, 22:48 UTC | Passed | 402 | 228 ms |
| 15 Oct 2026, 18:45 UTC | Passed | 402 | 185 ms |
Price and payment address
- Price
- $0.039 per call on Base
- Pays to
- 0xec84…de28
No price or payment address changes recorded.
How we check
Up means the endpoint answered an unpaid test request with a valid x402 payment challenge. We never pay, so we can't see whether the paid response works.
Checks come from our server, about every 5 hours for this listing over the last 7 days. A failure can also mean the service blocks our checks. Two failed checks in a row count as an outage, which ends at the next passing check.
If you think a check is wrong, contact hello@toolvet.app. More on how we check and score. To see what an agent gets right now, check it yourself.