Flashbots Status - Incident history https://status.flashbots.net Flashbots Tue, 29 Sep 2026 08:06:24 +0000 Protect outage Type: Incident Duration: 5 minutes Affected Components: Protect Sep 29, 08:11:23 GMT+0 - Resolved - Protect is now operational! This update was created by an automated monitoring service. Sep 29, 08:06:24 GMT+0 - Investigating - Protect cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

Sep 29, 08:11:23 GMT+0
Resolved - Protect is now operational! This update was created by an automated monitoring service..

Sep 29, 08:06:24 GMT+0
Investigating - Protect cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 29 Sep 2026 08:06:24 +0000 https://status.flashbots.net/incident/cmume759o02m00wmof44u35b1 https://status.flashbots.net/incident/cmume759o02m00wmof44u35b1 Protect outage Type: Incident Duration: 5 minutes Affected Components: Protect Sep 29, 05:09:23 GMT+0 - Resolved - Protect is now operational! This update was created by an automated monitoring service. Sep 29, 05:04:31 GMT+0 - Investigating - Protect cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 5 minutes

Affected Components:

Sep 29, 05:09:23 GMT+0
Resolved - Protect is now operational! This update was created by an automated monitoring service..

Sep 29, 05:04:31 GMT+0
Investigating - Protect cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 29 Sep 2026 05:04:31 +0000 https://status.flashbots.net/incident/cmum7p9e100yg13objcks2mup https://status.flashbots.net/incident/cmum7p9e100yg13objcks2mup Protect outage Type: Incident Duration: 10 minutes Affected Components: Protect Aug 22, 03:18:24 GMT+0 - Resolved - Protect is now operational! This update was created by an automated monitoring service. Aug 22, 03:08:27 GMT+0 - Investigating - Protect cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 10 minutes

Affected Components:

Aug 22, 03:18:24 GMT+0
Resolved - Protect is now operational! This update was created by an automated monitoring service..

Aug 22, 03:08:27 GMT+0
Investigating - Protect cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sat, 22 Aug 2026 03:08:27 +0000 https://status.flashbots.net/incident/cmt3stma40y0j0kpbmc4ez8be https://status.flashbots.net/incident/cmt3stma40y0j0kpbmc4ez8be blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 1 day, 3 hours and 3 minutes Affected Components: blocks.flashbots.net Jul 28, 17:29:04 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 28, 17:02:02 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 1 day, 3 hours and 3 minutes

Affected Components:

Jul 28, 17:29:04 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 28, 17:02:02 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Thu, 28 Jul 2022 17:02:02 +0000 https://status.flashbots.net/incident/cl65a9raq696879uwn9mym1xmgi https://status.flashbots.net/incident/cl65a9raq696879uwn9mym1xmgi rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 5 hours Affected Components: rpc.flashbots.net Jul 20, 19:33:13 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 20, 19:28:14 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 5 hours

Affected Components:

Jul 20, 19:33:13 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 20, 19:28:14 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Wed, 20 Jul 2022 19:28:14 +0000 https://status.flashbots.net/incident/cl5tzyyli95332q4onu93a06x2 https://status.flashbots.net/incident/cl5tzyyli95332q4onu93a06x2 relay.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 8 hours and 29 minutes Affected Components: relay.flashbots.net Jul 20, 19:32:06 GMT+0 - Resolved - relay.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 20, 19:23:37 GMT+0 - Investigating - relay.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 8 hours and 29 minutes

Affected Components:

Jul 20, 19:32:06 GMT+0
Resolved - relay.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 20, 19:23:37 GMT+0
Investigating - relay.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Wed, 20 Jul 2022 19:23:37 +0000 https://status.flashbots.net/incident/cl5tzt17620591006lq0iqxnkf6 https://status.flashbots.net/incident/cl5tzt17620591006lq0iqxnkf6 blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 7 hours and 2 minutes Affected Components: blocks.flashbots.net Jul 18, 06:25:04 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 18, 06:18:02 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 7 hours and 2 minutes

Affected Components:

Jul 18, 06:25:04 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 18, 06:18:02 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Mon, 18 Jul 2022 06:18:02 +0000 https://status.flashbots.net/incident/cl5qcv1ou179262wtog1ty6ayi1 https://status.flashbots.net/incident/cl5qcv1ou179262wtog1ty6ayi1 blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 2 hours and 3 minutes Affected Components: blocks.flashbots.net Jul 11, 14:39:04 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 11, 14:37:01 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 2 hours and 3 minutes

Affected Components:

Jul 11, 14:39:04 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 11, 14:37:01 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Mon, 11 Jul 2022 14:37:01 +0000 https://status.flashbots.net/incident/cl5gulson12831w9n37fzj5uqd https://status.flashbots.net/incident/cl5gulson12831w9n37fzj5uqd blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 9 hours and 3 minutes Affected Components: blocks.flashbots.net Jul 5, 00:46:03 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 5, 00:37:01 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 9 hours and 3 minutes

Affected Components:

Jul 5, 00:46:03 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 5, 00:37:01 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 5 Jul 2022 00:37:01 +0000 https://status.flashbots.net/incident/cl57fyfes151443eqok50ftuf46 https://status.flashbots.net/incident/cl57fyfes151443eqok50ftuf46 blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 5 hours and 1 minute Affected Components: blocks.flashbots.net Jul 5, 00:28:03 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 5, 00:23:02 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 5 hours and 1 minute

Affected Components:

Jul 5, 00:28:03 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 5, 00:23:02 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 5 Jul 2022 00:23:02 +0000 https://status.flashbots.net/incident/cl57fgfr87265ewnbpjo1pzg8 https://status.flashbots.net/incident/cl57fgfr87265ewnbpjo1pzg8 blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 1 hour and 4 minutes Affected Components: blocks.flashbots.net Jul 5, 00:17:06 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jul 5, 00:16:02 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 1 hour and 4 minutes

Affected Components:

Jul 5, 00:17:06 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jul 5, 00:16:02 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 5 Jul 2022 00:16:02 +0000 https://status.flashbots.net/incident/cl57f7fz849640fsoh0fqe9ipt https://status.flashbots.net/incident/cl57f7fz849640fsoh0fqe9ipt Some services might currently be down due to ongoing Cloudflare issues Type: Incident Affected Components: rpc.flashbots.net Jun 21, 07:19:15 GMT+0 - Resolved - Cloudflare is currently having ongoing issues: [https://www.cloudflarestatus.com](https://www.cloudflarestatus.com) Type: Incident

Affected Components:

Jun 21, 07:19:15 GMT+0
Resolved - Cloudflare is currently having ongoing issues: [https://www.cloudflarestatus.com](https://www.cloudflarestatus.com).

]]> Tue, 21 Jun 2022 07:19:15 +0000 https://status.flashbots.net/incident/cl4nu5s2q67613m9n1jg328v9o https://status.flashbots.net/incident/cl4nu5s2q67613m9n1jg328v9o blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 1 day, 16 hours and 2 minutes Affected Components: blocks.flashbots.net Jun 21, 07:16:09 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jun 21, 06:36:07 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 1 day, 16 hours and 2 minutes

Affected Components:

Jun 21, 07:16:09 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jun 21, 06:36:07 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 21 Jun 2022 06:36:07 +0000 https://status.flashbots.net/incident/cl4nsmbaf1184106ejog1nolgto9 https://status.flashbots.net/incident/cl4nsmbaf1184106ejog1nolgto9 rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 1 day, 21 hours and 4 minutes Affected Components: rpc.flashbots.net Jun 21, 07:19:08 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Jun 21, 06:34:04 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 1 day, 21 hours and 4 minutes

Affected Components:

Jun 21, 07:19:08 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Jun 21, 06:34:04 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 21 Jun 2022 06:34:04 +0000 https://status.flashbots.net/incident/cl4nsjog186824ekn6klrk22tw https://status.flashbots.net/incident/cl4nsjog186824ekn6klrk22tw blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 8 hours and 3 minutes Affected Components: blocks.flashbots.net Jun 7, 07:21:04 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Jun 7, 07:13:01 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 8 hours and 3 minutes

Affected Components:

Jun 7, 07:21:04 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Jun 7, 07:13:01 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Tue, 7 Jun 2022 07:13:01 +0000 https://status.flashbots.net/incident/cl43trtxm585214cwlk74l6mjlt https://status.flashbots.net/incident/cl43trtxm585214cwlk74l6mjlt relay.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 10 hours and 2 minutes Affected Components: relay.flashbots.net May 9, 17:05:02 GMT+0 - Resolved - relay.flashbots.net is now operational! The issue was due to database slowness leading to connection exhaustion. A fix has been deployed handling this case much better. May 9, 16:51:00 GMT+0 - Investigating - relay.flashbots.net cannot be accessed at the moment and no bundles are being processed Type: Incident

Duration: 10 hours and 2 minutes

Affected Components:

May 9, 17:05:02 GMT+0
Resolved - relay.flashbots.net is now operational! The issue was due to database slowness leading to connection exhaustion. A fix has been deployed handling this case much better..

May 9, 16:51:00 GMT+0
Investigating - relay.flashbots.net cannot be accessed at the moment and no bundles are being processed.

]]> Mon, 9 May 2022 16:51:00 +0000 https://status.flashbots.net/incident/cl2yyskx4211953enooaep2any3 https://status.flashbots.net/incident/cl2yyskx4211953enooaep2any3 blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 5 hours and 1 minute Affected Components: blocks.flashbots.net Apr 17, 18:38:03 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Apr 17, 18:33:02 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 5 hours and 1 minute

Affected Components:

Apr 17, 18:38:03 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Apr 17, 18:33:02 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sun, 17 Apr 2022 18:33:02 +0000 https://status.flashbots.net/incident/cl23mlwb89535627ookyrpp8zqa https://status.flashbots.net/incident/cl23mlwb89535627ookyrpp8zqa blocks.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 4 hours and 2 minutes Affected Components: blocks.flashbots.net Apr 17, 02:07:03 GMT+0 - Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service. Apr 17, 02:03:01 GMT+0 - Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 4 hours and 2 minutes

Affected Components:

Apr 17, 02:07:03 GMT+0
Resolved - blocks.flashbots.net is now operational! This update was created by an automated monitoring service..

Apr 17, 02:03:01 GMT+0
Investigating - blocks.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sun, 17 Apr 2022 02:03:01 +0000 https://status.flashbots.net/incident/cl22n8q8i3855297ookrexltfqe https://status.flashbots.net/incident/cl22n8q8i3855297ookrexltfqe rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 2 hours and 23 minutes Affected Components: rpc.flashbots.net Mar 4, 16:54:27 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Mar 4, 16:52:04 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 2 hours and 23 minutes

Affected Components:

Mar 4, 16:54:27 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Mar 4, 16:52:04 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Fri, 4 Mar 2022 16:52:04 +0000 https://status.flashbots.net/incident/cl0cnmkzh147787499onmksoablg https://status.flashbots.net/incident/cl0cnmkzh147787499onmksoablg rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 21 hours Affected Components: rpc.flashbots.net Feb 26, 05:41:03 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Feb 26, 05:20:04 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 21 hours

Affected Components:

Feb 26, 05:41:03 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Feb 26, 05:20:04 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sat, 26 Feb 2022 05:20:04 +0000 https://status.flashbots.net/incident/cl03e9jl8783900enoai411tt7f https://status.flashbots.net/incident/cl03e9jl8783900enoai411tt7f rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 2 hours and 2 minutes Affected Components: rpc.flashbots.net Feb 26, 05:14:04 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Feb 26, 05:12:03 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 2 hours and 2 minutes

Affected Components:

Feb 26, 05:14:04 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Feb 26, 05:12:03 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sat, 26 Feb 2022 05:12:03 +0000 https://status.flashbots.net/incident/cl03dz8cp1059515d5odhfi5nrg5 https://status.flashbots.net/incident/cl03dz8cp1059515d5odhfi5nrg5 rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 9 hours Affected Components: rpc.flashbots.net Feb 26, 04:56:03 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Feb 26, 04:47:04 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 9 hours

Affected Components:

Feb 26, 04:56:03 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Feb 26, 04:47:04 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sat, 26 Feb 2022 04:47:04 +0000 https://status.flashbots.net/incident/cl03d33vd448948enoa5y2jteag https://status.flashbots.net/incident/cl03d33vd448948enoa5y2jteag rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 11 hours and 1 minute Affected Components: rpc.flashbots.net Feb 26, 04:39:05 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Feb 26, 04:28:05 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 11 hours and 1 minute

Affected Components:

Feb 26, 04:39:05 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Feb 26, 04:28:05 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sat, 26 Feb 2022 04:28:05 +0000 https://status.flashbots.net/incident/cl03ceoyw612746d5odycoyuvft https://status.flashbots.net/incident/cl03ceoyw612746d5odycoyuvft rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 4 hours Affected Components: rpc.flashbots.net Feb 26, 04:24:03 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Feb 26, 04:20:04 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 4 hours

Affected Components:

Feb 26, 04:24:03 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Feb 26, 04:20:04 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sat, 26 Feb 2022 04:20:04 +0000 https://status.flashbots.net/incident/cl03c4dvk175040enoaieq0pd0e https://status.flashbots.net/incident/cl03c4dvk175040enoaieq0pd0e rpc.flashbots.net isn't accessible at the moment (automated) Type: Incident Duration: 4 minutes Affected Components: rpc.flashbots.net Feb 5, 17:09:09 GMT+0 - Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service. Feb 5, 17:09:06 GMT+0 - Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service. Type: Incident

Duration: 4 minutes

Affected Components:

Feb 5, 17:09:09 GMT+0
Resolved - rpc.flashbots.net is now operational! This update was created by an automated monitoring service..

Feb 5, 17:09:06 GMT+0
Investigating - rpc.flashbots.net cannot be accessed at the moment. This incident was created by an automated monitoring service..

]]> Sat, 5 Feb 2022 17:09:06 +0000 https://status.flashbots.net/incident/ckza3ch1h293780p9lwkgwduwb2 https://status.flashbots.net/incident/ckza3ch1h293780p9lwkgwduwb2