Network · data from 2026-11-12
AS269144 SILVANET
Registry name: AS269144 - SILVANET PROVEDOR DE INTERNET LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269144, 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.
| 2804:6014:c000::/34 | No ROA | Nonecovered by 2804:6014::/32 | 634 100% |
| 2804:6014:100::/40 | No ROA | Nonecovered by 2804:6014::/32 | 631 99% |
| 2804:6014:200::/40 | No ROA | Nonecovered by 2804:6014::/32 | 631 99% |
| 2804:6014:300::/40 | No ROA | Nonecovered by 2804:6014::/32 | 631 99% |
| 45.179.241.0/24 | No ROA | Other IRR onlyTC | 672 100% |
| 45.179.242.0/24 | No ROA | Other IRR onlyTC | 670 100% |
| 45.179.240.0/24 | No ROA | Other IRR onlyTC | 669 99% |
| 45.179.243.0/24 | No ROA | Other IRR onlyRADB, TC | 668 99% |
| 2804:6014::/32 | No ROA | Other IRR onlyRADB, TC | 632 99% |
AS-SET
AS269144'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 21 are in fix.csv.
- ROA: none9
- Route object: none4
- Route object: RIR5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:6014:c000::/34 | No ROA covers it. Add a ROA for AS269144, maxLength 34. |
| Route object: none | 2804:6014:c000::/34 | No route object for it. A route object for 2804:6014::/32 with origin AS269144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269144 in the RIR database for the space. |
| ROA: none | 2804:6014:100::/40 | No ROA covers it. Add a ROA for AS269144, maxLength 40. |
| Route object: none | 2804:6014:100::/40 | No route object for it. A route object for 2804:6014::/32 with origin AS269144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269144 in the RIR database for the space. |
| ROA: none | 2804:6014:200::/40 | No ROA covers it. Add a ROA for AS269144, maxLength 40. |
| Route object: none | 2804:6014:200::/40 | No route object for it. A route object for 2804:6014::/32 with origin AS269144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269144 in the RIR database for the space. |
| ROA: none | 2804:6014:300::/40 | No ROA covers it. Add a ROA for AS269144, maxLength 40. |
| Route object: none | 2804:6014:300::/40 | No route object for it. A route object for 2804:6014::/32 with origin AS269144 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269144 in the RIR database for the space. |
| ROA: none | 45.179.241.0/24 | No ROA covers it. Add a ROA for AS269144, maxLength 24. |
| Route object: RIR | 45.179.241.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 45.179.242.0/24 | No ROA covers it. Add a ROA for AS269144, maxLength 24. |
| Route object: RIR | 45.179.242.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 45.179.240.0/24 | No ROA covers it. Add a ROA for AS269144, maxLength 24. |
| Route object: RIR | 45.179.240.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 45.179.243.0/24 | No ROA covers it. Add a ROA for AS269144, maxLength 24. |
| Route object: RIR | 45.179.243.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:6014::/32 | No ROA covers it. Add a ROA for AS269144, maxLength 32. |
| Route object: RIR | 2804:6014::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269144 whose prefix no peer sees AS269144 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.179.240.0/22 | RADB, TC | No ROA |
| 45.179.240.0/23 | TC | No ROA |
| 45.179.242.0/23 | TC | 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.