bgpreport

Network · data from 2026-11-12

AS270242 AS270242 - EVEREST TELECOM EIRELI - ME

Registry name: AS270242 - EVEREST TELECOM EIRELI - ME, BR · not in PeeringDB

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

Announced routes

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

2804:6900::/34 No ROA Nonecovered by 2804:6900::/32 631 99% 67
2804:6900:4000::/34 No ROA Nonecovered by 2804:6900::/32 631 99% 67
2804:6900:8000::/34 No ROA Nonecovered by 2804:6900::/32 631 99% 67
2804:6900:c000::/34 No ROA Nonecovered by 2804:6900::/32 631 99% 67
187.62.69.0/24 No ROA Other IRR onlyRADB 666 99% 67
187.62.70.0/24 No ROA Other IRR onlyRADB 666 99% 67
187.62.71.0/24 No ROA Other IRR onlyRADB 666 99% 67
187.62.68.0/24 No ROA Other IRR onlyRADB 665 99% 67

AS-SET

AS270242 isn't in PeeringDB, where networks name their 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 18 are in fix.csv.

  • ROA: none8
  • Route object: none4
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:6900::/34No ROA covers it. Add a ROA for AS270242, maxLength 34.631 of 636
Route object: none2804:6900::/34No route object for it. A route object for 2804:6900::/32 with origin AS270242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270242 in the RIR database for the space.631 of 636
ROA: none2804:6900:4000::/34No ROA covers it. Add a ROA for AS270242, maxLength 34.631 of 636
Route object: none2804:6900:4000::/34No route object for it. A route object for 2804:6900::/32 with origin AS270242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270242 in the RIR database for the space.631 of 636
ROA: none2804:6900:8000::/34No ROA covers it. Add a ROA for AS270242, maxLength 34.631 of 636
Route object: none2804:6900:8000::/34No route object for it. A route object for 2804:6900::/32 with origin AS270242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270242 in the RIR database for the space.631 of 636
ROA: none2804:6900:c000::/34No ROA covers it. Add a ROA for AS270242, maxLength 34.631 of 636
Route object: none2804:6900:c000::/34No route object for it. A route object for 2804:6900::/32 with origin AS270242 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270242 in the RIR database for the space.631 of 636
ROA: none187.62.69.0/24No ROA covers it. Add a ROA for AS270242, maxLength 24.666 of 673
Route object: RIR187.62.69.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none187.62.70.0/24No ROA covers it. Add a ROA for AS270242, maxLength 24.666 of 673
Route object: RIR187.62.70.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none187.62.71.0/24No ROA covers it. Add a ROA for AS270242, maxLength 24.666 of 673
Route object: RIR187.62.71.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none187.62.68.0/24No ROA covers it. Add a ROA for AS270242, maxLength 24.665 of 673
Route object: RIR187.62.68.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673

Route objects not announced

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

187.62.68.0/22RADB, TCNo ROA
2804:6900::/32NTTCOM, RADB, TCNo ROA

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.