Network · data from 2026-11-12
AS33876 Dominios
Registry name: Flesk-AS DMNS - DOMINIOS, S.A., PT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33876, 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.
| 195.8.58.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 176.111.106.0/24 | Valid | Nonecovered by 176.111.104.0/22 | 673 100% |
| 91.198.47.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.8.30.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.126.168.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 176.61.144.0/21 | Valid | RIR databaseRIPE | 671 100% |
| 176.111.104.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.11.164.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.12.116.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.76.4.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 2a03:8bc0::/32 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS33876'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 5 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.8.58.0/23 | No ROA covers it. Add a ROA for AS33876, maxLength 23. |
| Route object: none | 176.111.106.0/24 | No route object for it. A route object for 176.111.104.0/22 with origin AS33876 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33876 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS33876 whose prefix no peer sees AS33876 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.12.119.0/24 | RADB | Valid |
| 185.76.4.0/23 | RIPE | Valid |
| 195.95.236.0/23 | RADB | No 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.