bgpreport

Network · data from 2026-11-12

AS62663 Telecall AS62663

Registry name: TELECALL - Telecall, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS62663, 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.
198.54.166.0/23 No ROA Other IRR onlyRADB 673 100% 67
2602:fe8a::/36 No ROA Other IRR onlyRADB 636 100% 68
198.54.166.0/24 No ROA Other IRR onlyRADB 3 0%low visibility 3
198.54.167.0/24 No ROA Other IRR onlyRADB 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS62663: AS-TLC. 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 (AS62663 isn't in the set, or no route object for AS62663 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 objectsAS62663 in itNot covered
AS-TLC RADB 5,2116186,854 Yes 0
ARIN (also) 114 Yes 0
RIPE (also) 112 No 4

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

  • ROA: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none198.54.166.0/23No ROA covers it. Add a ROA for AS62663, maxLength 23.673 of 673
Route object: RIR198.54.166.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2602:fe8a::/36No ROA covers it. Add a ROA for AS62663, maxLength 36.636 of 636
Route object: RIR2602:fe8a::/36Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none198.54.166.0/24No ROA covers it. Add a ROA for AS62663, maxLength 24.3 of 673
Route object: RIR198.54.166.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673
ROA: none198.54.167.0/24No ROA covers it. Add a ROA for AS62663, maxLength 24.3 of 673
Route object: RIR198.54.167.0/24Route object only in RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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