bgpreport

Network · data from 2026-11-12

AS64224 ATINET

Registry name: ATINET - ATI Solutions, US · PeeringDB

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

Announced routes

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

8.15.224.0/24 No ROA Other IRR onlyRADB 673 100% 67
8.15.225.0/24 No ROA Other IRR onlyRADB 673 100% 67
8.25.4.0/24 No ROA Other IRR onlyRADB 673 100% 67
204.48.112.0/24 Valid Nonecovered by 204.48.112.0/22 673 100% 67
147.92.56.0/24 Valid Other IRR onlyRADB 673 100% 67
147.92.57.0/24 Valid Other IRR onlyRADB 673 100% 67
147.92.58.0/24 Valid Other IRR onlyRADB 671 100% 68
147.92.59.0/24 Valid Other IRR onlyRADB 671 100% 68
2602:fe85:200::/39 Valid Other IRR onlyRADB 635 100% 69
2602:fe85::/36 Valid Other IRR onlyRADB 634 100% 70
2602:fe85::/39 Valid Other IRR onlyRADB 634 100% 70

AS-SET

PeeringDB's irr_as_set for AS64224: RS-AS64224. 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 (AS64224 isn't in the set, or no route object for AS64224 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 objectsAS64224 in itNot covered
RS-AS64224 A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none8.15.224.0/24No ROA covers it. Add a ROA for AS64224, maxLength 24.673 of 673
Route object: RIR8.15.224.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none8.15.225.0/24No ROA covers it. Add a ROA for AS64224, maxLength 24.673 of 673
Route object: RIR8.15.225.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none8.25.4.0/24No ROA covers it. Add a ROA for AS64224, maxLength 24.673 of 673
Route object: RIR8.25.4.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none204.48.112.0/24No route object for it. A route object for 204.48.112.0/22 with origin AS64224 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64224 in the RIR database for the space.673 of 673
Route object: RIR147.92.56.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR147.92.57.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR147.92.58.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR147.92.59.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2602:fe85:200::/39Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2602:fe85::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:fe85::/39Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

4.79.229.0/24RADBNo ROA
8.15.224.0/23ARIN, RADBNo ROA
8.25.4.0/23ARIN, RADBNo ROA
8.25.5.0/24RADBNo ROA
147.92.56.0/22ARIN, RADBValid
147.92.56.0/23RADBValid
147.92.58.0/23RADBValid
204.48.112.0/22ARINValid
2602:fe85::/32ARINValid
2602:fe85:1000::/36ARINValid
2602:fe85:1000::/48ARINValid
2602:fe85:1001::/48ARINValid
2602:fe85:2000::/36ARINValid
2602:fe85:2000::/48ARINValid

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.