bgpreport

Network · data from 2026-11-12

AS3480 PeachNet AS3480

Registry name: PEACHNET-AS3480 - Board of Regents of the University System of Georgia, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3480, 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.
193.43.244.0/24 Invalid: origin Other origin only 73 11% 37
193.43.245.0/24 Invalid: origin Other origin only 73 11% 37
185.162.148.0/24 Invalid: origin None 57 8%low visibility 33
185.162.149.0/24 Invalid: origin None 57 8%low visibility 33
193.43.246.0/24 Invalid: origin Other origin only 57 8%low visibility 33
193.43.247.0/24 Invalid: origin Other origin only 57 8%low visibility 33
185.162.150.0/24 Invalid: origin None 27 4%low visibility 22
185.162.150.0/23 Invalid: origin None 20 3%low visibility 18
168.8.0.0/14 No ROA Other IRR onlyALTDB 671 100% 69
168.12.0.0/16 No ROA Other IRR onlyALTDB 671 100% 69
198.72.64.0/22 No ROA Other IRR onlyALTDB 671 100% 69

AS-SET

PeeringDB's irr_as_set for AS3480: ALTDB::AS-PEACHNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS3480 isn't in the set, or no route object for AS3480 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS3480 in itNot covered
ALTDB::AS-PEACHNET ALTDB 24179 Yes 8

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

  • ROA: origin8
  • ROA: none3
  • Route object: none8
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: origin193.43.244.0/24ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.73 of 673
Route object: none193.43.244.0/24Route objects for it name AS34380. Add a route object with origin AS3480 in the RIR database for the space.73 of 673
ROA: origin193.43.245.0/24ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.73 of 673
Route object: none193.43.245.0/24Route objects for it name AS34380. Add a route object with origin AS3480 in the RIR database for the space.73 of 673
ROA: origin185.162.148.0/24ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.57 of 673
Route object: none185.162.148.0/24No route object for it. Add a route object with origin AS3480 in the RIR database for the space.57 of 673
ROA: origin185.162.149.0/24ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.57 of 673
Route object: none185.162.149.0/24No route object for it. Add a route object with origin AS3480 in the RIR database for the space.57 of 673
ROA: origin193.43.246.0/24ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.57 of 673
Route object: none193.43.246.0/24Route objects for it name AS34380. Add a route object with origin AS3480 in the RIR database for the space.57 of 673
ROA: origin193.43.247.0/24ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.57 of 673
Route object: none193.43.247.0/24Route objects for it name AS34380. Add a route object with origin AS3480 in the RIR database for the space.57 of 673
ROA: origin185.162.150.0/24ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.27 of 673
Route object: none185.162.150.0/24No route object for it. Add a route object with origin AS3480 in the RIR database for the space.27 of 673
ROA: origin185.162.150.0/23ROAs covering it name AS8075, AS34380, not AS3480. If AS3480 should announce it, add a ROA for AS3480.20 of 673
Route object: none185.162.150.0/23No route object for it. Add a route object with origin AS3480 in the RIR database for the space.20 of 673
ROA: none168.8.0.0/14No ROA covers it. Add a ROA for AS3480, maxLength 14.671 of 673
Route object: RIR168.8.0.0/14Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none168.12.0.0/16No ROA covers it. Add a ROA for AS3480, maxLength 16.671 of 673
Route object: RIR168.12.0.0/16Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none198.72.64.0/22No ROA covers it. Add a ROA for AS3480, maxLength 22.671 of 673
Route object: RIR198.72.64.0/22Route object only in ALTDB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS3480 is announced.

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.