bgpreport

Network · data from 2026-11-12

AS43341 MDlink online service center

Registry name: MDLINK MDlink online service center GmbH, DE · PeeringDB

10IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 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 AS43341, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS43341, 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.
45.141.38.0/23 Valid RIR databaseRIPE 673 100% 66
77.83.176.0/22 Valid RIR databaseRIPE 673 100% 66
88.150.0.0/17 Valid RIR databaseRIPE 673 100% 66
95.156.192.0/24 Valid RIR databaseRIPE 673 100% 66
185.188.120.0/22 Valid RIR databaseRIPE 673 100% 66
193.26.123.0/24 Valid RIR databaseRIPE 673 100% 66
194.45.154.0/24 Valid RIR databaseRIPE 673 100% 66
194.113.144.0/22 Valid RIR databaseRIPE 673 100% 66
213.211.192.0/19 Valid RIR databaseRIPE 673 100% 66
213.211.224.0/19 Valid RIR databaseRIPE 673 100% 66
2a03:5080::/32 Valid RIR databaseRIPE 636 100% 67
2a07:e300::/29 Valid RIR databaseRIPE 635 100% 67
2a09:8580::/29 Valid RIR databaseRIPE 635 100% 67
2a0c:d240::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS43341: RIPE::AS43341:AS-MDLINK. 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 (AS43341 isn't in the set, or no route object for AS43341 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 objectsAS43341 in itNot covered
RIPE::AS43341:AS-MDLINK In no IRR database read today.

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: not found1
ChangePrefix or setDetailFull-table peers
AS-SET: not foundRIPE::AS43341:AS-MDLINKPeeringDB names RIPE::AS43341:AS-MDLINK; no IRR database read has it.

Route objects not announced

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