bgpreport

Network · data from 2026-11-12

AS11281 ROBLOX-CORPORATE

Registry name: ROBLOX-CORPORATE - Roblox, US · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS11281, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11281, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
204.9.184.0/24 Valid Other IRR onlyRADB 672 100% 67
23.173.192.0/24 Valid Other IRR onlyRADB 670 100% 67
204.13.168.0/24 Valid Other IRR onlyRADB 670 100% 67
204.13.171.0/24 Valid Other IRR onlyRADB 670 100% 67
204.13.174.0/24 Valid Other IRR onlyRADB 670 100% 67
204.13.169.0/24 Valid Other IRR onlyRADB 669 99% 67
204.13.170.0/24 Valid Other IRR onlyRADB 668 99% 67
204.13.172.0/24 Valid Other IRR onlyRADB 668 99% 67
204.13.173.0/24 Valid Other IRR onlyRADB 668 99% 67
2602:801:1009::/48 Valid Other IRR onlyRADB 636 100% 67
2602:801:1008::/48 Valid Other IRR onlyRADB 635 100% 68
2602:801:1001::/48 Valid Other IRR onlyRADB 631 99% 67

AS-SET

AS11281's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 18 are in fix.csv.

  • Route object: RIR12
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR204.9.184.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR23.173.192.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.13.168.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.13.171.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.13.174.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR204.13.169.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR204.13.170.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR204.13.172.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR204.13.173.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2602:801:1009::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2602:801:1008::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2602:801:1001::/48Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

Route objects with origin AS11281 whose prefix no peer sees AS11281 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.142.220.0/23RADBNo ROA
204.9.184.0/23RADBValid
204.9.190.0/23RADBValid
204.9.190.0/24RADBValid
204.13.175.0/24RADBValid
2602:801:1000::/48RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.