bgpreport

Network · data from 2026-11-12

AS395363 Infoblox

Registry name: INFOBLOX-1 - Infoblox, Inc., US · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
7Route objects not announced registered with origin AS395363, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS395363, 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.
52.119.40.0/24 Valid Other IRR onlyNTTCOM, RADB, RIPE-NONAUTH 671 100% 66
185.173.184.0/24 Valid Other IRR onlyRADB 671 100% 67
185.173.185.0/24 Valid Other IRR onlyRADB 671 100% 67
2620:129:6010::/48 Valid Other IRR onlyNTTCOM, RADB 636 100% 68
2620:129:6000::/48 Valid Other IRR onlyNTTCOM, RADB 634 100% 68
2620:129:6020::/48 Valid Other IRR onlyNTTCOM, RADB 634 100% 68
103.80.4.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 66
103.80.5.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, RIPE-NONAUTH 671 100% 66
2400:4840:10::/48 Valid RIR databaseAPNIC, NTTCOM, RADB 636 100% 68
2400:4840::/48 Valid RIR databaseAPNIC, NTTCOM, RADB 634 100% 68

AS-SET

AS395363'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 13 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: RIR52.119.40.0/24Route object only in NTTCOM, RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR185.173.184.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR185.173.185.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2620:129:6010::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2620:129:6000::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2620:129:6020::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

52.119.40.0/22RADBNo ROA
52.119.42.0/24NTTCOM, RADBNo ROA
52.119.43.0/24NTTCOM, RADBNo ROA
103.80.4.0/22RADBNo ROA
103.80.7.0/24NTTCOM, RADBNo ROA
185.173.184.0/22RADBNo ROA
185.173.186.0/24RADBValid

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.