bgpreport

Network · data from 2026-11-12

AS13480 Ongoing Operations

Registry name: OGOPS - Ongoing Operations, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13480, 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.

64.212.63.0/24 No ROA Other IRR onlyRADB 673 100% 67
199.180.160.0/24 Valid Nonecovered by 199.180.160.0/22 673 100% 67
199.180.161.0/24 Valid Nonecovered by 199.180.160.0/22 673 100% 67
199.180.163.0/24 Valid Nonecovered by 199.180.160.0/22 673 100% 67
63.143.8.0/24 Valid Other IRR onlyRADB 673 100% 67
63.143.11.0/24 Valid Other IRR onlyRADB 673 100% 67
63.143.12.0/24 Valid Other IRR onlyRADB 673 100% 67
63.143.13.0/24 Valid Other IRR onlyRADB 673 100% 67
63.143.14.0/24 Valid Other IRR onlyRADB 673 100% 67
63.143.15.0/24 Valid Other IRR onlyRADB 673 100% 67
204.108.28.0/24 Valid Other IRR onlyRADB 673 100% 67
204.108.30.0/24 Valid Other IRR onlyNTTCOM, RADB 673 100% 67
74.119.46.0/24 Valid Other IRR onlyRADB 671 100% 67
63.143.0.0/21 Valid RIR databaseARIN 673 100% 67
204.108.31.0/24 Valid RIR databaseARIN 673 100% 67
208.95.56.0/24 Valid RIR databaseARIN 673 100% 67
208.95.57.0/24 Valid RIR databaseARIN 673 100% 67
208.95.58.0/24 Valid RIR databaseARIN 673 100% 67
204.108.29.0/24 Valid RIR databaseARIN 672 100% 67
63.143.0.0/24 Valid RIR databaseARIN 671 100% 67
63.143.1.0/24 Valid RIR databaseARIN 671 100% 67
63.143.2.0/24 Valid RIR databaseARIN 671 100% 67
63.143.3.0/24 Valid RIR databaseARIN 671 100% 67
63.143.5.0/24 Valid RIR databaseARIN 671 100% 67
63.143.7.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS13480'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 30 are in fix.csv.

  • ROA: none1
  • Route object: none3
  • Route object: RIR10
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none64.212.63.0/24No ROA covers it. Add a ROA for AS13480, maxLength 24.673 of 673
Route object: RIR64.212.63.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none199.180.160.0/24No route object for it. A route object for 199.180.160.0/22 with origin AS13480 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13480 in the RIR database for the space.673 of 673
Route object: none199.180.161.0/24No route object for it. A route object for 199.180.160.0/22 with origin AS13480 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13480 in the RIR database for the space.673 of 673
Route object: none199.180.163.0/24No route object for it. A route object for 199.180.160.0/22 with origin AS13480 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13480 in the RIR database for the space.673 of 673
Route object: RIR63.143.8.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR63.143.11.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR63.143.12.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR63.143.13.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR63.143.14.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR63.143.15.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.108.28.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR204.108.30.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR74.119.46.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

12.179.248.0/22NTTCOMNo ROA
12.179.250.0/24RADBNo ROA
63.143.0.0/20ARINValid
63.143.4.0/24ARINValid
63.143.6.0/24ARINValid
63.143.9.0/24RADBValid
63.143.10.0/24RADBValid
74.119.44.0/22ARINValid
74.119.44.0/24NTTCOM, RADBValid
74.119.45.0/24RADBValid
199.180.160.0/22ARIN, RADBValid
204.108.28.0/22ARINValid
204.225.146.0/23RADBNo ROA
204.225.146.0/24RADBNo ROA
204.225.147.0/24RADBNo ROA
208.95.56.0/22ARINValid

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.