bgpreport

Network · data from 2026-11-12

AS36165 ITM TELECOM

Registry name: ITM-TELECOM - ITM TELECOM, US · PeeringDB

11IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
4Route objects not announced registered with origin AS36165, seen from no peer

Announced routes

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

64.212.72.0/24 Valid Other IRR onlyRADB 667 99% 68
64.212.73.0/24 Valid Other IRR onlyRADB 667 99% 68
64.212.74.0/24 Valid Other IRR onlyRADB 667 99% 68
64.212.75.0/24 Valid Other IRR onlyRADB 667 99% 68
64.212.76.0/24 Valid Other IRR onlyRADB 667 99% 68
64.212.77.0/24 Valid Other IRR onlyRADB 667 99% 68
64.212.78.0/24 Valid Other IRR onlyRADB 667 99% 68
64.212.79.0/24 Valid Other IRR onlyRADB 667 99% 68
23.168.112.0/24 Valid RIR databaseARIN, RADB 667 99% 68
38.95.93.0/24 Valid RIR databaseARIN, RADB 667 99% 68
64.190.166.0/24 Valid RIR databaseARIN, RADB 667 99% 68

AS-SET

PeeringDB's irr_as_set for AS36165: ARIN::AS-36165. 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 (AS36165 isn't in the set, or no route object for AS36165 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 objectsAS36165 in itNot covered
ARIN::AS-36165 ARIN1 member set in no database: AS269879:AS-CONE 3145 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 13 are in fix.csv.

  • Route object: RIR8
  • AS-SET: missing member1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR64.212.72.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR64.212.73.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR64.212.74.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR64.212.75.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR64.212.76.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR64.212.77.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR64.212.78.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR64.212.79.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
AS-SET: missing memberARIN::AS-36165AS-36165 (ARIN) lists AS269879:AS-CONE; no IRR database read has it.

Route objects not announced

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

64.212.72.0/21ARINNo ROA
208.81.175.0/24RADBNo ROA
2001:470:340::/48ARINValid
2606:5c0::/32ARIN, RADBValid

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.