bgpreport

Network · data from 2026-11-12

AS198611 M-Networks Sp. z o.o.

Registry name: M-NETWORKS-AS M-Networks Sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198611, 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.
91.240.131.0/24 Invalid: origin None 2 0%low visibility 2
2a0c:44c0:1::/48 No ROA RIR databaseRIPE 1 0%low visibility 1
2a0c:44c0:2::/48 No ROA RIR databaseRIPE 1 0%low visibility 1
91.231.205.0/24 Valid RIR databaseRIPE 668 99% 67
91.237.68.0/24 Valid RIR databaseRIPE 668 99% 67
91.237.69.0/24 Valid RIR databaseRIPE 668 99% 67
91.237.70.0/24 Valid RIR databaseRIPE 668 99% 67
91.237.71.0/24 Valid RIR databaseRIPE 668 99% 67
185.212.67.0/24 Valid RIR databaseRIPE 668 99% 67
193.239.204.0/24 Valid RIR databaseRIPE 668 99% 67
2001:67c:16f8::/48 Valid RIR databaseRIPE 1 0%low visibility 1
2001:67c:2ad8::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS198611: AS-MNETWORKS. 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 (AS198611 isn't in the set, or no route object for AS198611 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 objectsAS198611 in itNot covered
AS-MNETWORKS RIPE 2112 Yes 1

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: origin1
  • ROA: none2
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin91.240.131.0/24ROAs covering it name AS47544, not AS198611. If AS198611 should announce it, add a ROA for AS198611.2 of 673
Route object: none91.240.131.0/24No route object for it. Add a route object with origin AS198611 in the RIR database for the space.2 of 673
ROA: none2a0c:44c0:1::/48No ROA covers it. Add a ROA for AS198611, maxLength 48.1 of 636
ROA: none2a0c:44c0:2::/48No ROA covers it. Add a ROA for AS198611, maxLength 48.1 of 636

Route objects not announced

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

2a10:f781:10:639f::/64RIPENo 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.