Network · data from 2026-11-12
AS200529 ASR INFOPRO
Registry name: ASR-INFOPRO ASR INFOPRO s.a r.l., FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200529, 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.
| 2a0c:9a46:700::/48 | Valid | Nonecovered by 2a0c:9a46:700::/40 | 634 100% |
| 2a0c:9a46:78b::/48 | Valid | Nonecovered by 2a0c:9a46:700::/40 | 634 100% |
| 2a0c:9a46:78c::/48 | Valid | Nonecovered by 2a0c:9a46:700::/40 | 634 100% |
| 2a0c:9a46:78d::/48 | Valid | Nonecovered by 2a0c:9a46:700::/40 | 634 100% |
| 2a0e:7d47::/48 | Valid | Nonecovered by 2a0e:7d47::/32 | 634 100% |
| 2a0e:b107:1d30::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a0c:9a46:78a::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS200529: AS-ASR-NET. 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 (AS200529 isn't in the set, or no route object for AS200529 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 | AS200529 in it | Not covered |
|---|---|---|---|---|---|
| AS-ASR-NET | RIPE | 3 | 1 | No | 7 |
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 10 are in fix.csv.
- Route object: none5
- AS-SET: own ASN1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a0c:9a46:700::/48 | No route object for it. A route object for 2a0c:9a46:700::/40 with origin AS200529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200529 in the RIR database for the space. |
| Route object: none | 2a0c:9a46:78b::/48 | No route object for it. A route object for 2a0c:9a46:700::/40 with origin AS200529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200529 in the RIR database for the space. |
| Route object: none | 2a0c:9a46:78c::/48 | No route object for it. A route object for 2a0c:9a46:700::/40 with origin AS200529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200529 in the RIR database for the space. |
| Route object: none | 2a0c:9a46:78d::/48 | No route object for it. A route object for 2a0c:9a46:700::/40 with origin AS200529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200529 in the RIR database for the space. |
| Route object: none | 2a0e:7d47::/48 | No route object for it. A route object for 2a0e:7d47::/32 with origin AS200529 covers it (filters allowing more-specifics accept it). Add a route object with origin AS200529 in the RIR database for the space. |
| AS-SET: own ASN | AS-ASR-NET | AS200529 isn't in AS-ASR-NET (RIPE) once expanded. Add AS200529 to it. |
Route objects not announced
Route objects with origin AS200529 whose prefix no peer sees AS200529 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a06:2c80:2000::/36 | RIPE | Valid |
| 2a06:2c80:6000::/36 | RIPE | Valid |
| 2a0c:9a46:700::/40 | RIPE | Valid |
| 2a0e:7d47::/32 | 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.