bgpreport

Network · data from 2026-11-12

AS270466 AS270466 - EASY NET LTDA - ME

Registry name: AS270466 - EASY NET LTDA - ME, BR · not in 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
0Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS270466, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270466, 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.
200.106.136.0/22 No ROA Other IRR onlyTC 668 99% 67
2804:6c68::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
200.106.136.0/23 No ROA Other IRR onlyTC 207 31% 56
200.106.138.0/23 No ROA Other IRR onlyTC 207 31% 56

AS-SET

AS270466 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: none4
  • Route object: RIR4
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none200.106.136.0/22No ROA covers it. Add a ROA for AS270466, maxLength 22.668 of 673
Route object: RIR200.106.136.0/22Route object only in TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:6c68::/32No ROA covers it. Add a ROA for AS270466, maxLength 32.635 of 636
Route object: RIR2804:6c68::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none200.106.136.0/23No ROA covers it. Add a ROA for AS270466, maxLength 23.207 of 673
Route object: RIR200.106.136.0/23Route object only in TC. Add it in the RIR database for the space.207 of 673
ROA: none200.106.138.0/23No ROA covers it. Add a ROA for AS270466, maxLength 23.207 of 673
Route object: RIR200.106.138.0/23Route object only in TC. Add it in the RIR database for the space.207 of 673

Route objects not announced

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

200.106.136.0/24TCNo ROA
200.106.137.0/24TCNo ROA
200.106.138.0/24TCNo ROA
200.106.139.0/24TCNo ROA
2804:6c68::/33TCNo ROA
2804:6c68::/34TCNo ROA
2804:6c68:4000::/34TCNo ROA
2804:6c68:8000::/33TCNo ROA
2804:6c68:8000::/34TCNo ROA
2804:6c68:c000::/34TCNo 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.