FBK Status - Incident history https://fbk.instatus.com FBK Sun, 24 May 2026 17:30:00 +0000 Server Migration Type: Maintenance 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 Type: Maintenance

Duration: 44 minutes

Affected Components:

<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Identified</strong> - Migration of FBK to a different physical server is beginning, and the bot will go offline for this maintenance soon..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>17:30:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>18:14:10</var> GMT+0</small><br><strong>Completed</strong> - Migration has been completed and the bot is online. Monitoring for issues .</p> ]]> Sun, 24 May 2026 17:30:00 +0000 https://fbk.instatus.com/maintenance/cmpjyn2cr0fqmqnb0klt8x1s0 https://fbk.instatus.com/maintenance/cmpjyn2cr0fqmqnb0klt8x1s0 Unplanned Outage Type: Maintenance 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. Type: Maintenance

Duration: 11 days and 16 hours

Affected Components: , , , , , , , , , ,

<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>22:00:00</var> GMT+0</small><br><strong>Completed</strong> - There was an unexpected delay during upgrades resulting in downtime until the outage was reported..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>17:20:00</var> GMT+0</small><br><strong>Identified</strong> - There was an unexpected delay during upgrades resulting in downtime until the outage was reported..</p> ]]> Wed, 6 May 2026 17:20:00 +0000 https://fbk.instatus.com/maintenance/cmoux6lr1017j1370v988xwcb https://fbk.instatus.com/maintenance/cmoux6lr1017j1370v988xwcb AniList API Outage Type: Incident 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 - Type: Incident

Duration: 4 days, 5 hours and 55 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 28</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br><strong>Identified</strong> - .</p> <p><small>May <var data-var='date'> 2</var>, <var data-var='time'>18:55:03</var> GMT+0</small><br><strong>Resolved</strong> - .</p> ]]> Tue, 28 Apr 2026 13:00:00 +0000 https://fbk.instatus.com/incident/cmoisyuys07lqkatdxmagtwtp https://fbk.instatus.com/incident/cmoisyuys07lqkatdxmagtwtp Network Connectivity Type: Incident 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. Type: Incident

Duration: 1 hour and 55 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>12:50:00</var> GMT+0</small><br><strong>Identified</strong> - .</p> <p><small>Jan <var data-var='date'> 28</var>, <var data-var='time'>14:45:00</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> ]]> Wed, 28 Jan 2026 12:50:00 +0000 https://fbk.instatus.com/incident/cmky58vef0hddytjoezhodkj0 https://fbk.instatus.com/incident/cmky58vef0hddytjoezhodkj0 Twitter Access Blocked Type: Incident 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 Type: Incident

Duration: 21 hours and 50 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>18:00:00</var> GMT+0</small><br><strong>Investigating</strong> - The bot began receiving errors when attempting to access Twitter feeds. .</p> <p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>14:52:25</var> GMT+0</small><br><strong>Identified</strong> - Bot will be offline for a short time while updating components to restore the Twitter tracker.</p> <p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>15:50:12</var> GMT+0</small><br><strong>Resolved</strong> - Twitter component updated to work around blocking, tweet posting should be catching up now .</p> ]]> Fri, 5 Dec 2025 18:00:00 +0000 https://fbk.instatus.com/incident/cmiug5hyu003rlezm65rk0m70 https://fbk.instatus.com/incident/cmiug5hyu003rlezm65rk0m70 YouTube Chat Integrations Disabled (HoloChats) Type: Incident 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 - Type: Incident

Duration: 6 days, 23 hours and 14 minutes

<p><small>Oct <var data-var='date'> 31</var>, <var data-var='time'>00:46:00</var> GMT+0</small><br><strong>Investigating</strong> - 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. .</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>05:36:11</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>06:19:46</var> GMT+0</small><br><strong>Monitoring</strong> - Temporarily routing chat through my home network..</p> <p><small>Nov <var data-var='date'> 7</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br><strong>Resolved</strong> - .</p> ]]> Fri, 31 Oct 2025 00:46:00 +0000 https://fbk.instatus.com/incident/cmhio7qxr02jdc0wp6e2nd2qz https://fbk.instatus.com/incident/cmhio7qxr02jdc0wp6e2nd2qz AniList API temporarily disabled Type: Incident 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. Type: Incident

Duration: 15 hours and 41 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 28</var>, <var data-var='time'>11:00:00</var> GMT+0</small><br><strong>Identified</strong> - AniList has temporarily disabled their API due to stability issues, and the tracker will not be available until resolved by them..</p> <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>02:40:31</var> GMT+0</small><br><strong>Resolved</strong> - AniList has re-enabled their API and the tracker is functional. .</p> ]]> Sun, 28 Sep 2025 11:00:00 +0000 https://fbk.instatus.com/incident/cmg4ctuzo02gk13ww27kbtxc9 https://fbk.instatus.com/incident/cmg4ctuzo02gk13ww27kbtxc9 Partial Extended Bot Outage Type: Incident 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. Type: Incident

Duration: 19 hours and 50 minutes

Affected Components: , , , ,

<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Investigating</strong> - 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. .</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>03:15:25</var> GMT+0</small><br><strong>Monitoring</strong> - System rebooted and issue was different than expected, further investigation will be needed. All FBK nstances should now be available. .</p> <p><small>Sep <var data-var='date'> 27</var>, <var data-var='time'>04:50:00</var> GMT+0</small><br><strong>Resolved</strong> - Connection appears stable, please report any further issues..</p> ]]> Fri, 26 Sep 2025 09:00:00 +0000 https://fbk.instatus.com/incident/cmg1fao6h02fy10mxecp3f27g https://fbk.instatus.com/incident/cmg1fao6h02fy10mxecp3f27g