bgpreport

Network · data from 2026-11-12

AS33167 SWOCA-TWASSIGNED - Southwest Ohio Computer Association

Registry name: SWOCA-TWASSIGNED - Southwest Ohio Computer Association, US · not in PeeringDB

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

Announced routes

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

216.48.132.0/23 No ROA Nonecovered by 216.48.128.0/21 671 100% 69
216.48.134.0/23 No ROA Nonecovered by 216.48.128.0/21 671 100% 68
216.48.138.0/24 No ROA Nonecovered by 216.48.136.0/21 671 100% 68
216.48.128.0/20 No ROA Other IRR onlyALTDB, RADB 671 100% 69
199.18.71.0/24 No ROA Other IRR onlyALTDB, RADB 467 69% 67
192.147.116.0/24 No ROA Other IRR onlyRADB 461 68% 66
216.48.136.0/21 No ROA Other IRR onlyRADB 20 3%low visibility 18

AS-SET

AS33167 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 15 are in fix.csv.

  • ROA: none7
  • Route object: none3
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none216.48.132.0/23No ROA covers it. Add a ROA for AS33167, maxLength 23.671 of 673
Route object: none216.48.132.0/23No route object for it. A route object for 216.48.128.0/21 with origin AS33167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33167 in the RIR database for the space.671 of 673
ROA: none216.48.134.0/23No ROA covers it. Add a ROA for AS33167, maxLength 23.671 of 673
Route object: none216.48.134.0/23No route object for it. A route object for 216.48.128.0/21 with origin AS33167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33167 in the RIR database for the space.671 of 673
ROA: none216.48.138.0/24No ROA covers it. Add a ROA for AS33167, maxLength 24.671 of 673
Route object: none216.48.138.0/24No route object for it. A route object for 216.48.136.0/21 with origin AS33167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33167 in the RIR database for the space.671 of 673
ROA: none216.48.128.0/20No ROA covers it. Add a ROA for AS33167, maxLength 20.671 of 673
Route object: RIR216.48.128.0/20Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.18.71.0/24No ROA covers it. Add a ROA for AS33167, maxLength 24.467 of 673
Route object: RIR199.18.71.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.467 of 673
ROA: none192.147.116.0/24No ROA covers it. Add a ROA for AS33167, maxLength 24.461 of 673
Route object: RIR192.147.116.0/24Route object only in RADB. Add it in the RIR database for the space.461 of 673
ROA: none216.48.136.0/21No ROA covers it. Add a ROA for AS33167, maxLength 21.20 of 673
Route object: RIR216.48.136.0/21Route object only in RADB. Add it in the RIR database for the space.20 of 673

Route objects not announced

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

216.48.128.0/21RADBNo 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.