bgpreport

Network · data from 2026-11-12

AS25853 Ellijay Telephone Company

Registry name: ELJY30540 - Ellijay Telephone Company, US · PeeringDB

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

Announced routes

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

24.75.160.0/20 Valid Other IRR onlyRADB 671 100% 67
24.239.16.0/20 Valid Other IRR onlyRADB 671 100% 67
65.7.128.0/17 Valid Other IRR onlyRADB 671 100% 67
69.85.96.0/19 Valid Other IRR onlyRADB 671 100% 67
69.194.16.0/20 Valid Other IRR onlyRADB 671 100% 67
72.18.96.0/20 Valid Other IRR onlyRADB 671 100% 67
72.255.192.0/20 Valid Other IRR onlyRADB 671 100% 67
89.239.48.0/20 Valid Other IRR onlyRADB 671 100% 67
151.210.96.0/19 Valid Other IRR onlyRADB 671 100% 67
172.102.160.0/19 Valid Other IRR onlyRADB 671 100% 67
207.89.0.0/20 Valid Other IRR onlyRADB 671 100% 67
104.36.188.0/22 Valid Other IRR onlyRADB 669 99% 67
162.212.184.0/22 Valid Other IRR onlyRADB 669 99% 67
192.119.2.0/23 Valid Other IRR onlyRADB 669 99% 67
192.206.70.0/23 Valid Other IRR onlyRADB 669 99% 67
204.16.12.0/22 Valid Other IRR onlyRADB 669 99% 67
206.126.226.0/23 Valid Other IRR onlyRADB 669 99% 67
66.44.192.0/19 Valid Other IRR onlyRADB 668 99% 67
2604:c380::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS25853: RADB::AS25853:AS-ALL. 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 (AS25853 isn't in the set, or no route object for AS25853 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 objectsAS25853 in itNot covered
RADB::AS25853:AS-ALL RADB 3236 Yes 0

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

  • Route object: RIR19
ChangePrefix or setDetailFull-table peers
Route object: RIR24.75.160.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR24.239.16.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR65.7.128.0/17Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.85.96.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR69.194.16.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR72.18.96.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR72.255.192.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR89.239.48.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR151.210.96.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.102.160.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR207.89.0.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR104.36.188.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR162.212.184.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR192.119.2.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR192.206.70.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR204.16.12.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR206.126.226.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR66.44.192.0/19Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2604:c380::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS25853 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.