bgpreport

Network · data from 2026-11-12

AS273518 MHEKS Provedor de Internet

Registry name: AS273518 - MHEKS Provedor de Internet, BR · PeeringDB

0IPv4 routes
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No 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 AS273518, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273518, 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:8fe0::/32 No ROA Other IRR onlyRADB, TC 627 99% 69

AS-SET

AS273518'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 6 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2804:8fe0::/32No ROA covers it. Add a ROA for AS273518, maxLength 32.627 of 636
Route object: RIR2804:8fe0::/32Route object only in RADB, TC. Add it in the RIR database for the space.627 of 636

Route objects not announced

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

2804:3398:2::/48RADBNo ROA
2804:8fe0::/33RADB, TCNo ROA
2804:8fe0::/41RADB, TCNo ROA
2804:8fe0:8000::/33RADB, 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.