bgpreport

Network · data from 2026-11-12

AS273659 MLINK TELECOM

Registry name: AS273659 - MLINK TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273659, 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:8a48::/32 No ROA Other IRR onlyRADB, TC 634 100% 69
2804:8a48::/33 No ROA Other IRR onlyTC 634 100% 69
2804:8a48:4000::/34 No ROA Other IRR onlyTC 634 100% 69
2804:8a48:8000::/33 No ROA Other IRR onlyTC 634 100% 69
2804:8a48:8000::/34 No ROA Other IRR onlyTC 634 100% 69
2804:8a48:c000::/34 No ROA Other IRR onlyTC 634 100% 69
79.182.49.0/24 Valid RIR databaseRADB, RIPE 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS273659: AS273659:AS-MLINK-TELECOM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS273659 isn't in the set, or no route object for AS273659 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS273659 in itNot covered
AS273659:AS-MLINK-TELECOM TC 139 Yes 0

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 14 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:8a48::/32No ROA covers it. Add a ROA for AS273659, maxLength 32.634 of 636
Route object: RIR2804:8a48::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:8a48::/33No ROA covers it. Add a ROA for AS273659, maxLength 33.634 of 636
Route object: RIR2804:8a48::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:8a48:4000::/34No ROA covers it. Add a ROA for AS273659, maxLength 34.634 of 636
Route object: RIR2804:8a48:4000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:8a48:8000::/33No ROA covers it. Add a ROA for AS273659, maxLength 33.634 of 636
Route object: RIR2804:8a48:8000::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:8a48:8000::/34No ROA covers it. Add a ROA for AS273659, maxLength 34.634 of 636
Route object: RIR2804:8a48:8000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:8a48:c000::/34No ROA covers it. Add a ROA for AS273659, maxLength 34.634 of 636
Route object: RIR2804:8a48:c000::/34Route object only in TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

204.157.236.0/24RADBNo ROA
2804:8a48::/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.