Duration: 44 minutes

Affected Components: FBK Discord Bot

May 24, 17:30:00 GMT+0
Identified - Migration of FBK to a different physical server is beginning, and the bot will go offline for this maintenance soon..

May 24, 17:30:01 GMT+0
Identified - Maintenance is now in progress.

May 24, 18:14:10 GMT+0
Completed - Migration has been completed and the bot is online. Monitoring for issues .

Duration: 11 days and 16 hours

Affected Components: FBK Discord Bot, MyAnimeList, Kick.com, Web Server, TwitCasting, YouTube, Bluesky, Kitsu, AniList, FBK Server Box, Twitter/X

May 6, 22:00:00 GMT+0
Completed - There was an unexpected delay during upgrades resulting in downtime until the outage was reported..

May 6, 17:20:00 GMT+0
Identified - There was an unexpected delay during upgrades resulting in downtime until the outage was reported..

Duration: 4 days, 5 hours and 55 minutes

Affected Components: AniList

Apr 28, 13:00:00 GMT+0
Identified - .

May 2, 18:55:03 GMT+0
Resolved - .

Duration: 1 hour and 55 minutes

Affected Components: FBK Discord Bot

Jan 28, 12:50:00 GMT+0
Identified - .

Jan 28, 14:45:00 GMT+0
Resolved - The bot's server became unable to resolve web addresses. A reboot was given as soon as the report was noticed, and the bot is back online. The cause is unknown. .

Duration: 21 hours and 50 minutes

Affected Components: FBK Discord Bot, Twitter/X

Dec 5, 18:00:00 GMT+0
Investigating - The bot began receiving errors when attempting to access Twitter feeds. .

Dec 6, 14:52:25 GMT+0
Identified - Bot will be offline for a short time while updating components to restore the Twitter tracker.

Dec 6, 15:50:12 GMT+0
Resolved - Twitter component updated to work around blocking, tweet posting should be catching up now .

Duration: 6 days, 23 hours and 14 minutes

Oct 31, 00:46:00 GMT+0
Investigating - At the exact time on this incident, YouTube had pushed a change which disabled FBK's YouTube chat integration. Features which rely on this are no longer functioning at this time. The library FBK was using for chat was very reliable but was archived 4 years ago and will not be updated. I have unfortunately discovered this at the very end of my weekend here, so I do not know how long it will take to look into this. If this is a simple change I can adapt it to myself, then I may be able to address it during the week but otherwise I will need to evaluate the viability for another method of scraping YouTube chat. .

Nov 3, 05:36:11 GMT+0
Identified - Upon some testing, there in fact seems to have not been a breaking change. The service works immediately from my home setup. YouTube instead seems to have pushed some more aggressive blocking of bots accessing chat. The bot has never been blocked from accessing chat before. This is more straightforward to work around, but is actually a worse situation in terms of this being likely to happen again and breaking other bots as well..

Nov 3, 06:19:46 GMT+0
Monitoring - Temporarily routing chat through my home network..

Nov 7, 00:00:00 GMT+0
Resolved - .

Duration: 15 hours and 41 minutes

Affected Components: AniList

Sep 28, 11:00:00 GMT+0
Identified - AniList has temporarily disabled their API due to stability issues, and the tracker will not be available until resolved by them..

Sep 29, 02:40:31 GMT+0
Resolved - AniList has re-enabled their API and the tracker is functional. .

Duration: 19 hours and 50 minutes

Affected Components: FBK Discord Bot, Twitter/X, YouTube, , FBK Server Box, Service Integrations →

Sep 26, 09:00:00 GMT+0
Investigating - FBK is experiencing network connection issues of an unknown cause. Some bot instances are completely offline and online instances may still experience tracker delay. Restart will occur in approximately 4 hours from this notice to resolve this issue, and further investigation to prevent future extended downtime like this will occur over the weekend. .

Sep 27, 03:15:25 GMT+0
Monitoring - System rebooted and issue was different than expected, further investigation will be needed. All FBK nstances should now be available. .

Sep 27, 04:50:00 GMT+0
Resolved - Connection appears stable, please report any further issues..