bgpreport

Network · data from 2026-11-12

AS271578 M A Link Telecomunicacoes Consortes

Registry name: AS271578 - M A Link Telecomunicacoes Consortes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271578, 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:7db8::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:7db8::/33 No ROA Other IRR onlyTC 354 56% 64

AS-SET

PeeringDB's irr_as_set for AS271578: AS271578:AS-LINKMAR. 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 (AS271578 isn't in the set, or no route object for AS271578 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 objectsAS271578 in itNot covered
AS271578:AS-LINKMAR TC 172220 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 5 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:7db8::/32No ROA covers it. Add a ROA for AS271578, maxLength 32.635 of 636
Route object: RIR2804:7db8::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:7db8::/33No ROA covers it. Add a ROA for AS271578, maxLength 33.354 of 636
Route object: RIR2804:7db8::/33Route object only in TC. Add it in the RIR database for the space.354 of 636

Route objects not announced

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

2804:7db8:8000::/33TCNo 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.