Duration: 2 hours and 50 minutes

Affected Components: Public API, Website, reForge Captcha, Website, TweetSyncer, NetTrace, Auth System, Account Management

May 14, 11:15:00 GMT+0
Identified - We are currently performing scheduled maintenance to migrate all our websites and Discord bots to the same robust infrastructure powering ThundraHost, our hosting company. This upgrade ensures improved performance, reliability, and scalability across all services. We expect minimal downtime and will provide updates as we complete the process..

May 14, 11:15:01 GMT+0
Identified - Maintenance is now in progress.

May 14, 12:35:07 GMT+0
Identified - Great news— we've successfully migrated all Discord bots to the ThundraHost infrastructure. This step ensures they now run on the same high-performance, reliable platform as our hosting services. We're now proceeding with the migration of all websites, with minimal expected disruption. Updates will follow as we progress..

May 14, 14:04:55 GMT+0
Completed - All migrations are now complete. All Discord bots and websites have been successfully transferred to the ThundraHost infrastructure, delivering enhanced performance, reliability, and scalability. Services are fully operational with no disruptions. Thank you for your patience during this upgrade..

Duration: 25 minutes

Affected Components: reForge Captcha

May 3, 14:42:38 GMT+0
Investigating - We are currently investigating reports of issues affecting the reForge Captcha verification process. While the captcha itself continues to function, some users may experience verification failures when attempting to log in, register, or perform other actions on sites that use reForge Captcha. Our team is actively working to identify the root cause and implement a fix. We will provide updates as more information becomes available..

May 3, 14:50:16 GMT+0
Monitoring - It appears that the reForge Captcha verification process is now functioning as expected again. The issue may have been caused by Cloudflare temporarily blocking requests or a similar external factor. We will continue to monitor the situation to ensure stability..

May 3, 15:07:26 GMT+0
Resolved - This incident has been resolved..

Duration: 3 days, 13 hours and 28 minutes

Affected Components: reForge Captcha

Apr 30, 16:00:00 GMT+0
Identified - We will be performing scheduled maintenance to upgrade our authentication system across reForge Captcha, reForge Consent, and NexSub. During this maintenance period, login, registration, profile management, and password reset functionality will remain available. However, you may notice ongoing changes as we roll out the new system. Some features may intermittently stop working or behave unexpectedly during the transition. What’s changing: We are introducing **NolarFlow (**[**nolarflow.site**](http://nolarflow.site)**)** as our new centralized account manager. Going forward, all authentication will be handled through NolarFlow, allowing you to access all our tools—including those requiring an account—using a single unified account. As part of this upgrade, we will also introduce **Single Sign-On (SSO)** support via NolarFlow. You will be able to connect and log in using providers such as Google, Discord, GitHub, and Twitch. This means multiple login options, all managed through one central system. Once the migration is complete, all platforms will route authentication through NolarFlow. We appreciate your patience while we roll out these improvements..

Apr 27, 02:32:08 GMT+0
Completed - Maintenance has completed successfully..

Duration: 2 hours and 41 minutes

Affected Components: reForge Captcha

Apr 22, 13:00:00 GMT+0
Identified - We will perform planned maintenance to update reForge Captcha and reForge Consent. During this window we are implementing AES‑256‑GCM encryption to protect sensitive data such as IP addresses, ensuring it remains encrypted at all times and is only decrypted for the account holder within the interface. Brief service interruptions may occur while the updates are applied..

Apr 22, 13:50:00 GMT+0
Identified - The maintenance is proceeding smoothly. We have successfully encrypted all site secret keys and are now moving on to encrypt API keys, 2FA secrets, and IP addresses. Thanks to the encrypt and decrypt helper functions we built, adding this protection is straightforward, and because reForge Consent is a fork of reForge Captcha we can reuse the same functions without any extra work. We’ve also prepared an encrypter page to migrate all existing data to the new encryption system with ease..

Apr 22, 15:09:00 GMT+0
Identified - We’re almost finished with the maintenance for reForge Captcha and will move on to reForge Consent shortly after. In a few weeks, we will schedule one more major maintenance window focused on maximizing security across our platform. During this larger update, we will enhance protection for sensitive data and account security. We will also include NexSub in this maintenance, adding encryption for secrets, passkey support, and 2FA functionality. Please note that passkeys and 2FA are already available for reForge Captcha and reForge Consent, so these changes will apply only to NexSub..

Apr 22, 15:41:00 GMT+0
Completed - The maintenance for reForge Captcha has been successfully completed. We have decided to postpone the updates for reForge Consent to the upcoming major maintenance window. This allows us to first improve the system and resolve any existing bugs before making significant changes to the database structure..

Duration: 7 days and 20 hours

Affected Components: reForge Captcha

Apr 10, 10:38:00 GMT+0
Identified - We will be performing scheduled maintenance to migrate and expand the reForge Captcha service infrastructure. During this window, reForge Captcha will be moved to Web Node 2 (EU) and Web Node 1 (US), bringing it in line with our standard multi-node deployment used by all other services. Additionally, DB 01 will be relocated to a centralized position, enabling all web nodes across EU and US regions to connect to a single unified database. We expect brief interruptions to the reForge Captcha service during this maintenance window. All other services remain unaffected..

Apr 10, 11:23:00 GMT+0
Identified - DB 01 has been successfully migrated and is now accessible to all web nodes across the EU and US regions. We are currently proceeding with the final phase of this maintenance window: migrating reForge Captcha to Web Node 2 (EU) and Web Node 1 (US) to complete the multi-node deployment. Brief interruptions to the reForge Captcha service may still occur during this phase. All other services are fully operational..

Apr 10, 13:46:00 GMT+0
Completed - The scheduled maintenance has been completed. reForge Captcha is now running on Web Node 1 (EU) and Web Node 1 (US). During this maintenance window, Web Node 2 (EU) was decommissioned due to technical issues, resulting in a single web node per region. We have identified an increase in database latency for the US web node connecting to DB 01 (EU). Our team is currently investigating the deployment of a dedicated DB 01 instance in the US region, which would be kept in real-time sync with the EU database. This approach introduces minor replication latency between servers, however end users will experience no noticeable impact as the databases remain up to date at all times. We will provide further updates as this investigation progresses..

Duration: 19 days, 4 hours and 10 minutes

Mar 20, 00:05:15 GMT+0
Resolved - On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues..

Mar 19, 16:25:04 GMT+0
Investigating - We are investigating reports of degraded performance for Git Operations.

Mar 19, 17:01:25 GMT+0
Investigating - We are redirecting traffic back to our Seattle region and customers should see a decrease in latency for Git operations.

Mar 20, 00:05:11 GMT+0
Investigating - We have reached stability with git operations through our changes deployed today..

Mar 19, 23:52:53 GMT+0
Investigating - We are seeing early signs of improvement. We are working on one more small change to further improve traffic routing on the west coast..

Mar 19, 18:27:25 GMT+0
Investigating - We are working to enable a new network path in the west coast to reduce load and will monitor the impact on latency for Git Operations.

Mar 19, 17:49:51 GMT+0
Investigating - We are still seeing elevated latency for Git operations in the west coast and are continuing to investigate.

Mar 19, 22:57:16 GMT+0
Investigating - We have completed the rollout of our new network path and are monitoring its impact..

Mar 19, 21:59:53 GMT+0
Investigating - We are beginning the rollout of our new network path. During this change, users will continue to see higher latency from the west coast. We will provide another update when the rollout is complete..

Duration: 7 days, 19 hours and 45 minutes

Mar 18, 22:36:34 GMT+0
Investigating - Git Operations is experiencing degraded performance. We are continuing to investigate..

Mar 18, 22:48:03 GMT+0
Investigating - We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate..

Mar 19, 00:56:37 GMT+0
Investigating - We continue to investigate the slow performance of Git Operations affecting the US West Coast..

Mar 18, 23:33:53 GMT+0
Investigating - We are continuing to investigate degraded performance for git operations from the US West Coast..

Mar 19, 00:10:19 GMT+0
Investigating - We continue to investigate degraded performance for git operations from the US West Coast..

Mar 19, 01:43:49 GMT+0
Investigating - We are seeing recovery in git operations for customers on the West Coast of the US..

Mar 18, 22:36:15 GMT+0
Investigating - We are investigating reports of impacted performance for some GitHub services..

Mar 19, 01:44:01 GMT+0
Resolved - On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7.