Basecamp outage history

Basecamp 5 Chat experienced an outage that blocked chat and ping features for users across multiple regions. Reports began around 8:00 AM UTC with messages and ping failures observed by users in India, Spain, Kenya, Egypt, Morocco, and beyond. The outage affected Basecamp 5 Chat specifically, leaving many users unable to send messages or receive chat notifications while other Basecamp services remained functional. Basecamp acknowledged the issue and said they were investigating reports that Basecamp 5 Chat is offline.

StatusGator detected issues 18 minutes 22 seconds before the official acknowledgment, at 8:05 AM UTC. The Basecamp status page then escalated the incident to a warning at 8:24 AM UTC and service was restored by 8:28 AM UTC. The outage lasted roughly 28 minutes and affected messaging and ping features across Europe, Africa, Asia, and the Middle East.

Basecamp's Fizzy component underwent a short maintenance window that briefly disrupted that feature. The incident began at 6:03 PM UTC when Fizzy entered maintenance, and the window lasted about ten minutes, ending at 6:13 PM UTC with Fizzy returning to normal operation. The status history shows Fizzy moving from up to maintenance and back to up, with other Basecamp services remaining available during this period.

Basecamp's HEY component was briefly placed into maintenance, causing a short period of unavailability for the HEY service. The maintenance window began at 4:03 AM UTC and concluded at 4:18 AM UTC, with HEY returning to full operation shortly after.

Basecamp experienced a brief maintenance window affecting the Fizzy component. The maintenance began at 3:58 PM UTC and the component returned to normal operation at 4:13 PM UTC, lasting roughly 15 minutes. After the window, Fizzy resumed full functionality and Basecamp services continued normally.

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.