bgpreport

Network · data from 2026-11-12

AS270036 270036

Registry name: AS270036 - NORTVCOM, SOCIEDAD ANONIMA, GT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270036, 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.
38.19.8.0/22 No ROA None 673 100% 67
179.60.226.0/24 Valid Nonecovered by 179.60.224.0/22 673 100% 67
179.60.227.0/24 Valid Nonecovered by 179.60.224.0/22 673 100% 67
179.60.224.0/24 Valid Nonecovered by 179.60.224.0/22 661 98% 67
179.60.225.0/24 Valid Nonecovered by 179.60.224.0/22 661 98% 67
2803:95e0::/32 Valid Other IRR onlyRADB 634 100% 67

AS-SET

AS270036's PeeringDB record names no AS-SET.

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: none1
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.19.8.0/22No ROA covers it. Add a ROA for AS270036, maxLength 22.673 of 673
Route object: none38.19.8.0/22No route object for it. Add a route object with origin AS270036 in the RIR database for the space.673 of 673
Route object: none179.60.226.0/24No route object for it. A route object for 179.60.224.0/22 with origin AS270036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270036 in the RIR database for the space.673 of 673
Route object: none179.60.227.0/24No route object for it. A route object for 179.60.224.0/22 with origin AS270036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270036 in the RIR database for the space.673 of 673
Route object: none179.60.224.0/24No route object for it. A route object for 179.60.224.0/22 with origin AS270036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270036 in the RIR database for the space.661 of 673
Route object: none179.60.225.0/24No route object for it. A route object for 179.60.224.0/22 with origin AS270036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270036 in the RIR database for the space.661 of 673
Route object: RIR2803:95e0::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

179.60.224.0/22RADBValid

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.