Network · data from 2026-11-12
AS265686 PROVIDERS
Registry name: AS265686 - PROVIDERS S.A., AR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265686, 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.
| 181.94.252.0/24 | Valid | Nonecovered by 181.94.252.0/22 | 666 99% |
| 181.94.253.0/24 | Valid | Nonecovered by 181.94.252.0/22 | 666 99% |
| 181.94.254.0/24 | Valid | Nonecovered by 181.94.252.0/22 | 666 99% |
| 181.94.255.0/24 | Valid | Nonecovered by 181.94.252.0/22 | 666 99% |
| 181.105.234.0/24 | Valid | Nonecovered by 181.105.234.0/23 | 666 99% |
| 45.6.4.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 45.6.5.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 45.6.7.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 45.6.6.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 200.43.0.0/22 | Valid | RIR databaseLACNIC | 669 99% |
| 181.105.221.0/24 | Valid | RIR databaseLACNIC | 666 99% |
| 190.228.177.0/24 | Valid | RIR databaseLACNIC | 665 99% |
AS-SET
AS265686's PeeringDB record names no AS-SET.
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 13 are in fix.csv.
- Route object: none5
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 181.94.252.0/24 | No route object for it. A route object for 181.94.252.0/22 with origin AS265686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265686 in the RIR database for the space. |
| Route object: none | 181.94.253.0/24 | No route object for it. A route object for 181.94.252.0/22 with origin AS265686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265686 in the RIR database for the space. |
| Route object: none | 181.94.254.0/24 | No route object for it. A route object for 181.94.252.0/22 with origin AS265686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265686 in the RIR database for the space. |
| Route object: none | 181.94.255.0/24 | No route object for it. A route object for 181.94.252.0/22 with origin AS265686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265686 in the RIR database for the space. |
| Route object: none | 181.105.234.0/24 | No route object for it. A route object for 181.105.234.0/23 with origin AS265686 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265686 in the RIR database for the space. |
| Route object: RIR | 45.6.4.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.5.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.7.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.6.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS265686 whose prefix no peer sees AS265686 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.6.4.0/22 | LACNIC, RADB | Valid |
| 181.94.252.0/22 | LACNIC | Valid |
| 181.105.233.0/24 | LACNIC | Valid |
| 181.105.234.0/23 | 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.