We're back up again now, may need a little more downtime but will try to schedule it at the weekend.

is down right now for a quick bit of emergency maintainence, won't be long, sorry for the inconvenience!.

RT @OpenSourceColl: We're building shared infrastructure for those seeking to identify, secure and sustain critical open source components.….

Happy New Year! We've just finished upgrading to Rails 7 and Ruby 3.1 🎉.

RT @teabass: Any @octoboxio users with access to Microsoft Edge feeling brave?

The first version of the Octobox Browser extension is now available to install:. Firefox: Chrome: Any feedback and bug reports much appreciated on the repository:

Today we rolled out some visual updates to better align with recent changes GitHub has made, lots more updates planned for November 🚢

RT @teabass: This week I'm working on a browser extension to integrate @octoboxio more directly into your GitHub triage workflows: https://….

RT @jongallant: I've turned off #GitHub email notifications and only use @octoboxio now. It's a todo list for your notifications, you can….

RT @BenJam: Today @octoboxio gave $10,000 to its dependencies to highlight that it's just as important to support the software we *use* as….

RT @teabass: GitHub hasn't made any of their new Notifications features available via the API, so @octoboxio can't properly sync with the n….

And we're back, sorry for the delay!.

We're about to do some server maintenance on the service will be unavailable for an hour or so whilst we move some data around. We'll update here when it's completed.

We're currently investigating errors for some users. Likely as a result of database maintenance Apologies if you are affected.

RT @BenJam: I sat down with the lovely folks of Sustain Our Software to talk about @octoboxio, GitHub sponsors and much more besides. Check….

@heroku The background workers are grinding through the queue, so things may take a little longer to update, should be caught up within 10 minutes or so.

Everything should be getting back to normal now. The cause was that the notifications table grew too large for the indexes to fit into ram, so it started to swap which killed the performance. The solution was a quick database upgrade, thanks @heroku!.

We're back! May go offline again in a few minutes though, sorry!.

Putting the site into maintenance mode briefly to continue investigating the performance degradation.

We're seeing lots of timeouts on investigating the cause now.