Basecamp Outage History

Basecamp experienced a brief loading outage for a subset of users, with connections timing out and some reports of 522 errors. StatusGator detected the issue at Feb 27, 2026 12:25 PM UTC, ahead of any official acknowledgement, and the incident lasted from 12:25 PM UTC to 12:41 PM UTC (about 16 minutes). Seven user reports were logged, beginning around 12:15 PM UTC and increasing by 12:30 PM UTC, with observations from Delhi, Chennai, Ahmedabad, and Dehradun indicating a regional impact in India. No Basecamp status updates were published during the event.

Basecamp users experienced slow performance and frequent crashes, with Bengaluru-based reports indicating the service was not accessible. An Early Warning Signal was detected from Feb 26, 2026 12:42 PM UTC and ended at Feb 26, 2026 12:44 PM UTC, preceding any official acknowledgment on Basecamp's status page. The earliest user observations appeared around 12:30 PM UTC. No official status updates were posted during this period, leaving the full scope and restoration timeline unclear. The impact points to degraded usability for project collaboration, with reports suggesting issues were noticeable to users relying on Basecamp, though the global reach cannot be confirmed from the available data.

Basecamp's Fizzy component briefly entered maintenance, potentially impacting related functionality. The maintenance began at Feb 19, 2026 3:18 AM UTC and ended at Feb 19, 2026 3:23 AM UTC, lasting about 5 minutes. The provider issued 2 status updates during the incident and restored normal service once maintenance completed.

Basecamp experienced a brief maintenance window affecting the Fizzy component. The status changed from up to maintenance at Feb 19, 2026 3:03 AM UTC and returned to up at Feb 19, 2026 3:13 AM UTC, for a total duration of about 10 minutes. The Fizzy component was briefly unavailable during the window, and service returned to normal shortly after.

Basecamp experienced a brief maintenance window affecting the Fizzy component. The maintenance began at 12:18 AM UTC and ended at 12:33 AM UTC, lasting about 15 minutes. The Fizzy component was taken offline for maintenance and brought back online after the window. Two official status updates were posted during the event, reflecting the maintenance and the subsequent restoration to normal operation.

Basecamp reported a brief maintenance window for the Fizzy component, with the status moving from up to maintenance at Feb 13, 2026 12:03 AM UTC and returning to up at Feb 13, 2026 12:23 AM UTC—a duration of about 20 minutes. The maintenance was planned, and there was no broader outage; user reporting during the period was limited.

Basecamp's Highrise component experienced a brief outage, rendering Highrise-related features inaccessible within Basecamp for about 5 minutes. Users attempting to access Highrise during the window would have seen errors before service was restored.

According to Basecamp's status page, Highrise went down at 3:53 AM UTC and came back up at 3:58 AM UTC. The incident prompted an investigation, and the status page issued two updates during the event. The outage lasted roughly 5 minutes and was limited to the Highrise component, with no indication of impact on other Basecamp services.

Basecamp 2 underwent a scheduled maintenance window that briefly affected access. The status page showed the component moving from up to maintenance with the message "In progress - Scheduled maintenance is currently in progress." The maintenance window lasted about 1 hour, from 9:03 AM UTC to 10:03 AM UTC UTC, after which Basecamp 2 returned to normal. The provider issued two status updates during the incident, confirming the maintenance and return to full service.

Basecamp 2 underwent a scheduled maintenance window. The window began at Dec 11, 2025 3:18 AM UTC and lasted about 1 hour, ending at Dec 11, 2025 4:18 AM UTC. During the window, Basecamp 2 was placed in maintenance and later returned to normal. The Basecamp status page issued two updates during the incident: one noting that maintenance was in progress and another confirming the service was back to normal.

Basecamp experienced an outage affecting six components: Highrise, Campfire, Basecamp 4, HEY, Basecamp 2, and Basecamp Classic. Users reported errors such as 500 Internal Server Errors and Cloudflare 500s when trying to access Basecamp and HEY services, disrupting project management, messaging, and collaboration features. The outage progressed from a full impact across these components to a partial recovery and eventual restoration.