Vendor reports: degradedResolved · vendor status “resolved”Official status API
Infinite Campus OneRoster Sync Error
Reported by Clever · Identity & Security · source last read just now
- Vendor start
- Jul 23, 2025, 18:55 UTC
- Vendor's clock
- Resolved
- Jul 24, 2025, 18:08 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 23 h 13 min
- From vendor start and resolution
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: Infinite Campus.[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2025-07-24 18:08 UTC · summary s1, evidence 4ea031b2d8f660bc
Evidence (7)
- E1Clever reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "Infinite Campus OneRoster Sync Error". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2025-07-23 18:55 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Infinite Campus. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2025-07-24 18:08 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Infinite Campus
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Clever is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Jul 23, 2025, 18:55 UTCVendor-reported startVendor time
- Jul 24, 2025, 18:08 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.