Get webhook notifications whenever Network & Infrastructure creates an incident, updates an incident, resolves an incident or changes a component status.
The new VAC in RBX is ready. This new version, based on our vRouters & FPGA solutions and 100G links, provides higher capacity and better mitigation functionalities, as we have better control over both the hardware and software.
We will start moving traffic from the previous VAC (vac1-*-a9/n7) to the new one (rbx-vac1-a75).
This page will be updated along the way, as we enable the new VAC for IP ranges.
--------------------------------------------
Traffic currently going through rbx-vac1-a75
--------------------------------------------
* All mitigation traffic
Update(s):
Date: 2017-04-20 06:51:28 UTC We are now moving the rest of the traffic to rbx-vac1-a75.
Date: 2017-04-18 12:59:56 UTC Added 144.217.0.0/16
Date: 2017-04-18 08:41:56 UTC Added 5.135.0.0/16 and 5.196.0.0/16
Date: 2017-04-14 09:17:23 UTC The latest issues on the FPGA, related to specific http packets, are now fixed.
We are resuming the traffic migration, starting with the previously migrated ranges :
167.114.0.0/16
158.69.0.0/16
192.99.0.0/16
149.56.0.0/16
37.187.0.0/16
Date: 2017-04-12 15:41:18 UTC We have observed some issues on Armor FPGA. We are moving the forced mitigation traffic back to vac1-0(b)-a9 for now. We captured a lot of metrics and information on the issue that will help us track the bug.
Date: 2017-04-07 08:01:37 UTC Putting back previous configured /16 networks
Date: 2017-04-04 08:12:35 UTC New FPGA issue encountered last night. Moving back traffic to vac1-0(b)-a9 until fixed.
Date: 2017-03-31 08:14:27 UTC Added 37.187.0.0/16 and 149.56.0.0/16
Date: 2017-03-30 10:39:43 UTC Adding 37.187.0.0/18 and 192.99.0.0/16
Date: 2017-03-30 10:21:19 UTC Added 158.69.0.0/16
Date: 2017-03-29 10:28:05 UTC We will now move some forced mitigation traffic to rbx-vac1-a75, starting with this range : 167.114.0.0/16
Date: 2017-03-28 15:41:42 UTC We've identified and fixed the issue in the FPGA's design, which was causing random pipeline stalls depending on the type and rate of traffic.
We're doing the final tests before moving forced mitigation traffic back to rbx-vac1-a75.
Date: 2017-03-21 17:08:42 UTC We have observed an issue on the FPGA in Armor. We moved the traffic back to vac1-0(b)-a9 while we investigate.
Date: 2017-03-21 14:40:53 UTC Adding 158.69.0.0/16
Date: 2017-03-21 10:53:37 UTC Moved forced mitigation traffic for 167.114.0.0/16
Date: 2017-03-21 10:31:27 UTC We are starting to move 'forced mitigation' traffic to rbx-vac1-a75.
Date: 2017-03-16 08:52:25 UTC All firewall and permanent mitigation traffic in RBX is now going through rbx-vac1-a75.
Next week we will start moving the traffic of IPs under forced mitigation.
Date: 2017-03-16 06:58:35 UTC We will now move the rest of the firewall and permanent mitigation traffic to rbx-vac1-a75
Date: 2017-03-15 10:09:04 UTC Adding 151.80.0.0/16
Date: 2017-03-15 09:06:23 UTC Adding 37.187.0.0/16
Date: 2017-03-15 08:39:49 UTC Adding 149.202.0.0/16
Date: 2017-03-15 07:42:12 UTC Adding 51.254.0.0/15
Date: 2017-03-14 11:51:23 UTC Added 144.217.0.0/16
Date: 2017-03-14 11:05:16 UTC Added 158.69.0.0/16 and 149.56.0.0/16
Date: 2017-03-14 09:02:45 UTC Added 167.114.0.0/16
Date: 2017-03-14 08:12:16 UTC Extended to 192.99.0.0/16
Date: 2017-03-14 07:33:05 UTC It seems to have fixed the issue. We're putting back traffic.
Date: 2017-03-14 07:18:25 UTC We are isolating rbx-vac1-a75 to update it to the latest version, to see if it fixes an issue we're seeing where OSPF neighbors on uplinks don't come back up automatically.
Date: 2017-03-13 11:19:00 UTC Extended to 192.99.0.0/17
Date: 2017-03-13 08:18:25 UTC Firewall and permanent mitigation traffic is now going through rbx-vac1-a75 for IPs in range 192.99.0.0/19
Date: 2017-03-10 18:06:31 UTC The issue is fixed, we will resume traffic switchover on Monday.
Date: 2017-03-09 09:18:52 UTC We rollbacked for now as we're seeing that some firewall rules are not properly blocking traffic.
Date: 2017-03-09 09:01:54 UTC We start moving some more traffic, for IPs in 192.99.0.0/16
Date: 2017-03-08 10:53:57 UTC The routing issue is fixed, we are resuming the operation
Date: 2017-03-08 10:03:34 UTC We are suspending this operation for now and rolled back, as we're seeing routing issues for IPs under antiphishing.
Date: 2017-03-08 09:14:17 UTC We are starting to move firewall and permanent mitigation traffic for IPs in range 192.99.0.0/24