RewindexChanges
What vendors changed
Every change Rewindex detected on vendor pricing, trust and legal pages and on status pages, newest first. Open one for the full diff.
Struck in red is what the vendor removed, blue is what they added.
Status pages are checked every 10 minutes, pricing, trust and legal pages once or twice a day. Times are UTC.
Follow every change in a feed reader: Atom feed.
Saturday, July 18
2 incident changes
- MaintenanceMajor incident
BrexScheduled Maintenance has been completed
Brex’s major-impact scheduled maintenance started July 18 at 07:01 UTC and was completed at 09:32 UTC, lasting 2 h 31 min. Customers were warned of brief interruptions accessing accounts via the dashboard or mobile app, and temporary unavailability of adding Brex cards to digital wallets such as Apple Pay or Google Pay.
- MajorMajor incident
Friday, July 17
14 incident changes
- OutageMajor incident
OptimizelyCampaign user interface partially unavailable
Optimizely reported a major partial outage of Campaign’s graphical interfaces for managing campaigns and content, including the EMEA Region interface, affecting only some users. It started at 2026-07-17 16:59 UTC and was marked resolved at 2026-07-17 17:17 UTC; the computed duration was 17 min. The vendor identified the affected component and resolved the problem.
- OutageMajor incident
GitLabElevated Errors Affecting GitLab Duo Custom Agents
GitLab Duo Custom Agents on GitLab.com experienced elevated errors in a major-impact incident from 2026-07-17 16:10 UTC to 2026-07-17 17:36 UTC, lasting 1 h 26 min. GitLab said it identified and mitigated the root cause, without specifying details; error rates returned to expected levels and service remained stable during monitoring.
- OutageCritical incident
BrexUsers are experiencing errors when viewing spend limit requests
Brex reported a critical Spend Management incident affecting access to new spend limit and spend limit increase requests on the dashboard’s Tasks page. It started at 2026-07-17 14:51 UTC and was resolved at 2026-07-17 15:32 UTC, lasting 40 min. Brex said it identified the root cause and resolved the issue but provided no details.
- OutageMajor incident
MakeLogin to make.com doesn't work
Make reported a major login outage on make.com starting 2026-07-17 14:22 UTC, resolved at 2026-07-17 15:09 UTC after 47 min. Scenario executions and webhooks were unaffected. Make identified the issue and applied a fix at 07-17 14:28 UTC, but did not state the cause.
- OutageMajor incident
MakeEtsy - default connection issues
Make reported a major outage affecting Etsy default connections, which returned an “invalid_target” error. It started at 2026-07-17 13:34 UTC and was resolved at 2026-07-22 12:07 UTC, lasting 4 days 22 h. Make attributed the issue to Etsy’s API and reported resolution after a temporary outage on Etsy’s side.
- CriticalCritical incident
- MajorMajor incident
- MajorMajor incident
- OutageMajor incident
Bunny.netUsers are unable to login to dash.bunny.net
Bunny.net reported a major Dashboard login outage from 2026-07-17 10:57 UTC to 2026-07-17 11:11 UTC, lasting 14 min. Users could not log in to dash.bunny.net, but services themselves were not disrupted. The issue was resolved after the Frontend team deployed a fix.
- MajorMajor incident
- OutageMajor incident
MakeLogin issues across multiple zones
Make reported a major login outage across multiple zones starting 2026-07-17 10:20 UTC, resolved at 2026-07-17 12:21 UTC, with a reported duration of 2 h 0 min. Scenario executions and webhooks were unaffected; Make applied a fix at 10:27 UTC and monitored results before resolving the incident.
- OutageMajor incident
SalesforceService Disruption: Core Service
Salesforce reported a critical Core Service disruption affecting 1 instance. It started at 2026-07-17 08:32 UTC and was resolved at 2026-07-17 08:40 UTC, lasting 8 min.
- OutageMajor incident
SalesforceService Disruption: Marketing Cloud Core Service
Salesforce reported a critical Marketing Cloud Core Service disruption affecting service access across 3 instances from 2026-07-17 05:28 UTC to 2026-07-17 05:48 UTC (20 min). A hardware failure impacted database infrastructure; Salesforce performed a database failover to restore services and reported all systems operating normally.
- OutageMajor incident
Discord reported a major API Errors incident from 2026-07-17 00:49 UTC to 2026-07-17 03:48 UTC, lasting 2 h 59 min. Discord identified an upstream latency issue, worked to mitigate its impacts, and marked the incident resolved.
Thursday, July 16
20 incident changes
- OutageCritical incident
SocketGithub App reports are failingEvent
Socket’s GitHub App reports failed in a critical-impact incident starting 2026-07-16 23:45 UTC, lasting 15 min and resolved at 2026-07-17 00:00 UTC. Socket attributed the failures to a high error rate on GitHub’s API and reported that GitHub restored service.
- OutageCritical incident
RenderGitHub outage affecting new service creation and service deploysEvent
Render reported a critical GitHub outage affecting new service creation and service deploys in Frankfurt, Ohio, Oregon, Singapore, and Virginia. It started at 2026-07-16 22:42 UTC and was resolved at 2026-07-17 00:14 UTC, lasting 1 h 32 min. GitHub reported degraded REST API availability and later said it had mitigated its incident.
- OutageMajor incident
Box[Medium] Issues with Box Edit and Microsoft Office Online
Box reported a major-impact outage affecting Box Edit and Microsoft Office Online, starting 2026-07-16 21:30 UTC and resolved at 2026-07-16 21:48 UTC (18 min). Box reported full functionality restored after remediation; its postmortem said some customers may have been unable to open or edit files through Open With integrations in the Box web application.
- MajorMajor incident
- OutageMajor incident
Gorgias[AI Agent][API] Elevated 5XX errors on the AI Agent API
Gorgias reported a major AI Agent API incident from 2026-07-16 13:56 UTC to 2026-07-16 14:26 UTC, lasting 29 min. Elevated 5XX errors meant some requests could fail or be delayed, and automated responses on affected tickets might not be sent. The incident was resolved; no specific cause or fix was disclosed.
- DegradationMajor incident
ChargebeeAPI Service Degradation
Chargebee reported major intermittent API request timeouts in the EU region from 15-7-2026 21:56:00 UTC to 16-07-2026 01:23:55 UTC. The incident record started and resolved at 2026-07-16 12:56 UTC (computed duration: 0 min); Chargebee said services were operating normally.
- DegradationMajor incident
WorkOS reported major email delivery delays affecting AuthKit, Core Services - AuthKit, Dashboard, and Supporting Services - Dashboard. The incident started at 2026-07-16 12:06 UTC and was resolved at 2026-07-16 12:21 UTC, lasting 15 min; WorkOS identified and resolved the issue but did not specify the cause or fix.
- CriticalCritical incident
- OutageMajor incident
SemgrepCustom SSO Login IssuesEvent
Customers with custom SSO configurations could not log in to Semgrep and saw 504 Gateway Timeout errors. The major-impact incident started at 2026-07-16 09:38 UTC and was resolved at 2026-07-16 12:46 UTC, lasting 3 h 7 min. Semgrep stated that the third-party vendor resolved it.
- OutageCritical incident
IterableIterable Application Issues in US DatacenterEvent
Iterable reported a critical US-region application and API outage starting 2026-07-16 09:27 UTC, resolved at 2026-07-16 10:07 UTC (39 min). Engineering deployed a fix across the US environment; successful logins resumed, and all sends and journeys that may have been delayed were processed by resolution.
- OutageMajor incident
RevenueCatSome users unable to login via single-sign-on (SSO)Event
RevenueCat reported a major SSO incident from 2026-07-16 09:13 UTC to 2026-07-16 10:47 UTC, lasting 1 h 34 min. Only organizations with SSO configured faced dashboard sign-in difficulties or interrupted sessions; SDKs, purchases, subscriptions, entitlements, APIs, analytics, and data exports were unaffected. The SSO provider implemented a fix, and the incident was resolved.
- OutageCritical incident
Rippling reported a critical incident in which some users saw "Access denied" when accessing Rippling. It started and was resolved at 2026-07-16 09:00 UTC, with a computed duration of 0 min; Rippling said the issue was fully mitigated and service was fully operational again.
- OutageMajor incident
AshbySome SSO sign-ins may failEvent
Ashby reported a major incident causing intermittent SSO login failures and timeouts from 2026-07-16 08:40 UTC to 2026-07-16 11:00 UTC, lasting 2 h 20 min. An upstream provider incident caused the failures; the provider resolved it, and Ashby confirmed recovery. Other sign-in methods, including magic-link sign-in, and the rest of Ashby were unaffected.
- OutageMajor incident
Verceland v0SAML Single Sign-On (SSO) errorsEvent
Vercel reported a major SAML Single Sign-On outage preventing SAML/SSO login and access to SSO-protected teams through the dashboard and CLI. It started at 2026-07-16 08:39 UTC and resolved at 2026-07-16 10:45 UTC, lasting 2 h 5 min. Vercel identified the root cause and implemented a fix but did not specify either.
- CriticalCritical incident
- CriticalCritical incident
- MajorMajor incident
- OutageMajor incident
WorkOSElevated Platform ErrorsEvent
WorkOS reported a major incident with elevated errors and latencies affecting AuthKit, SSO, Directory Sync, Audit Logs, Admin Portal and Dashboard. It started at 2026-07-16 08:26 UTC and resolved at 2026-07-16 10:44 UTC (2 h 17 min); WorkOS deployed a fix and published a postmortem.
- CriticalCritical incident
- OutageMajor incident
BigCommercePayment issues with Cybersource V2 provider
BigCommerce reported a major Checkout & Payment Processing outage causing transaction errors for merchants using Cybersource V2, starting 2026-07-16 00:39 UTC and lasting 9 h 53 min. BigCommerce attributed it to a provider outage; Cybersource applied mitigation, and BigCommerce reported no further payment-processing issues when it resolved the incident at 2026-07-16 10:33 UTC.
Wednesday, July 15
13 incident changes
- OutageMajor incident
RenderSome users enrolled in 2FA are experiencing login issues
Some users enrolled in 2FA experienced login loops accessing the Render Dashboard in a major-impact incident starting 2026-07-15 21:50 UTC. Render implemented a fix at 22:06 UTC and marked the incident resolved at 22:56 UTC; the computed duration was 1 h 5 min.
- OutageCritical incident
Muxvideo live and playback issues
Mux reported a critical incident affecting Mux Video - Live and Mux Video - VOD ingestion and playback, from 2026-07-15 19:13 UTC to 2026-07-16 17:07 UTC (21 h 53 min). A cloud infrastructure disruption in one availability zone affected some traffic; rerouting mitigated all customer impact by 07-16 00:21 UTC.
- DegradationMajor incident
CodecovDegraded processing service
Codecov reported a major processing-service degradation that could cause significant delays in coverage notifications on pull requests. It started at 2026-07-15 17:29 UTC and was resolved at 2026-07-16 00:24 UTC, lasting 6 h 54 min; Codecov reported implementing a fix and monitoring the results.
- OutageMajor incident
SalesforceMarketing Cloud Account Engagement Feature Disruption Application: Application
Salesforce reported a major Marketing Cloud Account Engagement Application disruption affecting 1 instance. It started at 2026-07-15 17:00 UTC and was resolved at 2026-07-15 17:01 UTC, lasting 1 min; no cause or fix was stated.
- OutageMajor incident
Temporal CloudCustomers in us-east-2 may experience some visibility related errors
Temporal Cloud reported a major incident causing visibility query errors for namespaces in us-east-2, starting 2026-07-15 16:55 UTC and resolving 2026-07-15 21:15 UTC (4 h 19 min). Temporal scaled up service for mitigation and advised MRN-enabled customers to fail over to passive regions. All namespaces failed over by Temporal were failed back before resolution.
- DegradationMajor incident
GorgiasAI Agent knowledge retrieval degradation
Gorgias reported major AI Agent knowledge-retrieval failures between 08:00 and 18:30 UTC on July 14: Help Center articles and guidance were intermittently missed, allowing context-only answers. A third-party ML provider infrastructure issue caused the failures; the incident record started and resolved at 2026-07-15 16:42 UTC (computed duration: 0 min).
- OutageMajor incident
PandaDocSome customers may experience Public API request failures or be unable to send documents through the platform
PandaDoc reported a major outage affecting Public API requests and document sending in US & Global, starting 2026-07-15 15:54 UTC and lasting 1 h 10 min. Public API access recovered at 16:12 UTC; new document creation and sending recovered at 16:22 UTC. Documents created during the incident were unblocked by full resolution at 2026-07-15 17:05 UTC.
- OutageMajor incident
GorgiasStore website and URLs sync failures
Gorgias reported a major outage affecting Knowledge content syncing from Store website and URLs sources for many stores; existing content was unaffected. It started 2026-07-15 10:18 UTC and lasted 2 days 3 h, resolving 2026-07-17 13:27 UTC after Gorgias deployed a fix for Store website sync issues.
- OutageMajor incident
SmartsheetSmartsheet US is not loading
Smartsheet US had a major outage from 2026-07-15 09:23 UTC to 2026-07-15 09:55 UTC (32 min), causing incomplete loading during login or item access. Smartsheet attributed authorization-check errors to a routine system update temporarily directing some requests to unavailable infrastructure; a fix was implemented and the incident resolved.
- CriticalCritical incident
- DegradationMajor incident
Box[Medium] Issues with Box Relay
Box Relay experienced a major-impact degradation starting 2026-07-15 04:14 UTC, affecting workflow functionality. The incident lasted 2 h 29 min and was resolved at 2026-07-15 06:43 UTC after a fix was implemented; Box confirmed full functionality was restored.
- OutageCritical incident
RenderRender Dashboard Unavailable
Render Dashboard was unavailable in a critical-impact incident starting 2026-07-15 00:22 UTC, resolved at 2026-07-15 00:54 UTC after 31 min. Render reported identifying the root cause and making a change that restored the dashboard, but did not specify the cause or fix.
- OutageMajor incident
Elastic CloudCloud Console Deployment Errors
Elastic Cloud reported a major Cloud Console incident affecting access to create, update, delete and view Elastic Cloud Hosted deployments. It started at 2026-07-15 00:15 UTC; management access was restored at 00:31 UTC, and the incident was resolved at 2026-07-15 01:12 UTC, with a reported duration of 56 min.