bgpreport

Network · data from 2026-11-12

AS270515 Enter Telecom

Registry name: AS270515 - Enter Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270515, 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.
187.49.152.0/23 Invalid: maxLength Nonecovered by 187.49.152.0/22 68 10% 32
187.49.154.0/23 Invalid: maxLength Nonecovered by 187.49.152.0/22 68 10% 34
187.49.155.0/24 Valid Other IRR onlyRADB 672 100% 67
187.49.154.0/24 Valid Other IRR onlyRADB 670 100% 67
187.49.152.0/24 Valid Other IRR onlyRADB 669 99% 67
187.49.153.0/24 Valid Other IRR onlyRADB 669 99% 67
2804:6d24::/32 Valid Other IRR onlyRADB 634 100% 69
187.49.152.0/22 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

AS270515'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 10 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: maxLength187.49.152.0/23ROA 187.49.152.0/22 AS270515 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 187.49.152.0/23.68 of 673
Route object: none187.49.152.0/23No route object for it. A route object for 187.49.152.0/22 with origin AS270515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270515 in the RIR database for the space.68 of 673
ROA: maxLength187.49.154.0/23ROA 187.49.152.0/22 AS270515 has maxLength 22; the route is a /23. Raise the maxLength, or add a ROA for 187.49.154.0/23.68 of 673
Route object: none187.49.154.0/23No route object for it. A route object for 187.49.152.0/22 with origin AS270515 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270515 in the RIR database for the space.68 of 673
Route object: RIR187.49.155.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.49.154.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR187.49.152.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR187.49.153.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:6d24::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR187.49.152.0/22Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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