Network · data from 2026-11-12

AS200625 MAPNET

Registry name: MA-P-NET Maciej Peczyk, PL · PeeringDB

0IPv4 routes

7IPv6 routes 100.0% RPKI valid · 85.7% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

2Route objects not announced registered with origin AS200625, seen from no peer

Announced routes

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


2a14:67c3:67c::/48	Valid	Nonecovered by 2a14:67c3:670::/44	634 100%	67
2a06:9801:8e::/48	Valid	RIR databaseRIPE	636 100%	67
2a0e:97c3::/48	Valid	RIR databaseRIPE	636 100%	67
2a14:67c3:670::/44	Valid	RIR databaseRIPE	634 100%	67
2a14:67c3:67a::/48	Valid	RIR databaseRIPE	634 100%	67
2a14:c380:1c0::/44	Valid	RIR databaseRIPE	634 100%	67
2a14:c380:1ca::/48	Valid	RIR databaseRIPE	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS200625: RIPE::AS200625:AS-CUST. 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 (AS200625 isn't in the set, or no route object for AS200625 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.

Name	Database	ASNs	Sets	Route objects	AS200625 in it	Not covered
RIPE::AS200625:AS-CUST	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS200625 in it

Not covered

RIPE::AS200625:AS-CUST

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

Route object: none1
AS-SET: not found1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
Route object: none	2a14:67c3:67c::/48	No route object for it. A route object for 2a14:67c3:670::/44 with origin AS200625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200625 in the RIR database for the space.	634 of 636
AS-SET: not found	RIPE::AS200625:AS-CUST	PeeringDB names RIPE::AS200625:AS-CUST; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

2a14:67c3:67c::/48

No route object for it. A route object for 2a14:67c3:670::/44 with origin AS200625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200625 in the RIR database for the space.

634 of 636

AS-SET: not found

RIPE::AS200625:AS-CUST

PeeringDB names RIPE::AS200625:AS-CUST; no IRR database read has it.

Route objects not announced

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


2a0e:97c3::/40	RIPE	Valid
2a14:67c3:677::/48	RIPE	Valid

2a0e:97c3::/40

RIPE

Valid

2a14:67c3:677::/48

RIPE

Valid

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.