bgpreport

Network · data from 2026-11-12

AS8657 MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA AS8657

Registry name: MEO-INTERNACIONAL MEO - SERVICOS DE COMUNICACOES E MULTIMEDIA S.A., PT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8657, 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.
185.96.172.0/22 Valid RIR databaseRIPE 668 99% 68
195.8.0.0/19 Valid RIR databaseRIPE 668 99% 68
217.168.112.0/21 Valid RIR databaseRIPE 668 99% 68
2001:15d8::/32 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS8657: RIPE::AS-CPRM RIPE::AS-CPRM-V6. 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 (AS8657 isn't in the set, or no route object for AS8657 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 objectsAS8657 in itNot covered
RIPE::AS-CPRM RIPElists itself further down1 member set in no database: AS-MTNNS 3161181,840 Yes 0
RIPE::AS-CPRM-V6 RIPE 1916,092 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 1 are in fix.csv.

  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRIPE::AS-CPRMAS-CPRM (RIPE) lists AS-MTNNS; no IRR database read has it.

Route objects not announced

Every route object with origin AS8657 is announced.

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.