bgpreport

Network · data from 2026-11-12

AS398795 TallWireless

Registry name: TALLWIRELESS - RFPT COMPANY LLC, US · PeeringDB

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

Announced routes

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

205.234.195.0/24 No ROA RIR databaseALTDB, ARIN 673 100% 67
2602:fd10:8ff::/48 Valid Nonecovered by 2602:fd10:8fe::/47 635 100% 68
2602:fd10:800::/44 Valid Other IRR onlyALTDB 634 100% 68
2602:fd10:800::/48 Valid Other IRR onlyALTDB, RADB 634 100% 68
2602:fd10:820::/44 Valid Other IRR onlyALTDB 634 100% 68
2602:fd10:860::/44 Valid Other IRR onlyALTDB 634 100% 68
207.2.126.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

PeeringDB's irr_as_set for AS398795: ALTDB::AS398795. 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 (AS398795 isn't in the set, or no route object for AS398795 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 objectsAS398795 in itNot covered
ALTDB::AS398795 A single AS number, not a set: AS398795 (this network), 12 route objects.

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: none1
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none205.234.195.0/24No ROA covers it. Add a ROA for AS398795, maxLength 24.673 of 673
Route object: none2602:fd10:8ff::/48No route object for it. A route object for 2602:fd10:8fe::/47 with origin AS398795 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398795 in the RIR database for the space.635 of 636
Route object: RIR2602:fd10:800::/44Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:fd10:800::/48Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:fd10:820::/44Route object only in ALTDB. Add it in the RIR database for the space.634 of 636
Route object: RIR2602:fd10:860::/44Route object only in ALTDB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2602:fd10:800::/40ARINValid
2602:fd10:840::/44RADBValid
2602:fd10:840::/48ALTDBValid
2602:fd10:862::/48ALTDBValid
2602:fd10:870::/44ALTDBValid
2602:fd10:8fe::/47RADBValid

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.