Network · data from 2026-11-12
AS269805 MEDIA COMMERCE MEDCOMM
Registry name: AS269805 - MEDIA COMMERCE MEDCOMM S.A, EC · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269805, 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.184.224.0/24 | Valid | Nonecovered by 45.184.224.0/22 | 668 99% |
| 45.184.225.0/24 | Valid | Nonecovered by 45.184.224.0/22 | 668 99% |
| 45.184.226.0/24 | Valid | Nonecovered by 45.184.224.0/22 | 668 99% |
| 45.184.227.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 179.43.95.0/24 | Valid | RIR databaseLACNIC, RADB | 668 99% |
| 2803:ab60::/32 | Valid | RIR databaseLACNIC, RADB | 634 100% |
| 2803:26e0:4000::/40 | Valid | RIR databaseLACNIC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS269805: AS269805:AS-PEERS. 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 (AS269805 isn't in the set, or no route object for AS269805 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 | AS269805 in it | Not covered |
|---|---|---|---|---|---|
| AS269805:AS-PEERS | LACNIC | 2 | 1 | Yes | 0 |
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 12 are in fix.csv.
- Route object: none3
- Route object: RIR1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.184.224.0/24 | No route object for it. A route object for 45.184.224.0/22 with origin AS269805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269805 in the RIR database for the space. |
| Route object: none | 45.184.225.0/24 | No route object for it. A route object for 45.184.224.0/22 with origin AS269805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269805 in the RIR database for the space. |
| Route object: none | 45.184.226.0/24 | No route object for it. A route object for 45.184.224.0/22 with origin AS269805 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269805 in the RIR database for the space. |
| Route object: RIR | 45.184.227.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269805 whose prefix no peer sees AS269805 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.184.224.0/22 | LACNIC, RADB | Valid |
| 181.188.246.0/28 | LACNIC | Valid |
| 190.89.47.0/24 | LACNIC | Valid |
| 2803:26e0::/32 | LACNIC | Valid |
| 2803:26e0:5000::/40 | LACNIC | Valid |
| 2803:26e0:5200::/40 | LACNIC | Valid |
| 2803:26e0:6000::/40 | LACNIC | Valid |
| 2803:26e0:6200::/40 | LACNIC | 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.