bgpreport

Network · data from 2026-11-12

AS5396 Retelit S.p.A. (formerly MC-Link)

Registry name: AS-IRIDEOS-MC Retelit Digital Services S.p.A., IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5396, 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.

92.60.76.0/24 Invalid: origin Other origin only 1 0%low visibility 1
185.63.87.0/24 No ROA None 2 0%low visibility 2
185.97.156.0/23 No ROA None 1 0%low visibility 1
185.97.158.0/23 No ROA None 1 0%low visibility 1
185.148.108.0/23 No ROA None 1 0%low visibility 1
185.148.110.0/23 No ROA None 1 0%low visibility 1
185.148.111.0/24 No ROA None 1 0%low visibility 1
91.225.180.0/22 Valid Other origin only 673 100% 67
195.130.195.0/24 Valid RIR databaseRIPE 671 100% 67
92.60.67.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
92.60.68.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
92.60.71.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS5396: RIPE::AS-MCLINK. 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 (AS5396 isn't in the set, or no route object for AS5396 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 objectsAS5396 in itNot covered
RIPE::AS-MCLINK RIPE 114 Yes 8

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

  • ROA: origin1
  • ROA: none6
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: origin92.60.76.0/24ROAs covering it name AS136809, AS201386, not AS5396. If AS5396 should announce it, add a ROA for AS5396.1 of 673
Route object: none92.60.76.0/24Route objects for it name AS136809, AS201386. Add a route object with origin AS5396 in the RIR database for the space.1 of 673
ROA: none185.63.87.0/24No ROA covers it. Add a ROA for AS5396, maxLength 24.2 of 673
Route object: none185.63.87.0/24No route object for it. Add a route object with origin AS5396 in the RIR database for the space.2 of 673
ROA: none185.97.156.0/23No ROA covers it. Add a ROA for AS5396, maxLength 23.1 of 673
Route object: none185.97.156.0/23No route object for it. Add a route object with origin AS5396 in the RIR database for the space.1 of 673
ROA: none185.97.158.0/23No ROA covers it. Add a ROA for AS5396, maxLength 23.1 of 673
Route object: none185.97.158.0/23No route object for it. Add a route object with origin AS5396 in the RIR database for the space.1 of 673
ROA: none185.148.108.0/23No ROA covers it. Add a ROA for AS5396, maxLength 23.1 of 673
Route object: none185.148.108.0/23No route object for it. Add a route object with origin AS5396 in the RIR database for the space.1 of 673
ROA: none185.148.110.0/23No ROA covers it. Add a ROA for AS5396, maxLength 23.1 of 673
Route object: none185.148.110.0/23No route object for it. Add a route object with origin AS5396 in the RIR database for the space.1 of 673
ROA: none185.148.111.0/24No ROA covers it. Add a ROA for AS5396, maxLength 24.1 of 673
Route object: none185.148.111.0/24No route object for it. Add a route object with origin AS5396 in the RIR database for the space.1 of 673
Route object: none91.225.180.0/22Route objects for it name AS3302. Add a route object with origin AS5396 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS5396 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.