bgpreport

Network · data from 2026-11-12

AS14278 BBOX-IT-AS-1 - Black Box Network Services

Registry name: BBOX-IT-AS-1 - Black Box Network Services, US · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 60.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS14278, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS14278, 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.29.247.0/24 No ROA Other origin onlycovered by 204.29.244.0/22 673 100% 67
204.89.138.0/24 No ROA Other origin only 673 100% 67
204.89.129.0/24 No ROA Other IRR onlyALTDB 673 100% 67
192.147.73.0/24 No ROA RIR databaseARIN 673 100% 67
204.29.243.0/24 No ROA RIR databaseARIN 673 100% 67

AS-SET

AS14278 isn't in PeeringDB, where networks name their 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 12 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none204.29.247.0/24No ROA covers it. Add a ROA for AS14278, maxLength 24.673 of 673
Route object: none204.29.247.0/24Route objects for it name AS17054. A route object for 204.29.244.0/22 with origin AS14278 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14278 in the RIR database for the space.673 of 673
ROA: none204.89.138.0/24No ROA covers it. Add a ROA for AS14278, maxLength 24.673 of 673
Route object: none204.89.138.0/24Route objects for it name AS17054. Add a route object with origin AS14278 in the RIR database for the space.673 of 673
ROA: none204.89.129.0/24No ROA covers it. Add a ROA for AS14278, maxLength 24.673 of 673
Route object: RIR204.89.129.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
ROA: none192.147.73.0/24No ROA covers it. Add a ROA for AS14278, maxLength 24.673 of 673
ROA: none204.29.243.0/24No ROA covers it. Add a ROA for AS14278, maxLength 24.673 of 673

Route objects not announced

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

130.45.41.0/24RADBNo ROA
169.206.0.0/16ARINNo ROA
204.29.244.0/22ARINNo ROA
204.29.248.0/24ARINNo ROA

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.