Network · data from 2026-11-12
AS268636 Netway soluções em redes de acesso e comunicação
Registry name: AS268636 - Netway solucoes em redes de acesso e comunicacao l, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268636, 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:543c::/34 | No ROA | Nonecovered by 2804:543c::/32 | 635 100% |
| 38.210.62.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 45.164.181.0/24 | Valid | Nonecovered by 45.164.180.0/22 | 671 100% |
| 45.164.180.0/24 | Valid | Nonecovered by 45.164.180.0/22 | 667 99% |
| 2804:543c:4000::/34 | Valid | Nonecovered by 2804:543c::/32 | 634 100% |
| 45.164.182.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 45.164.182.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.164.183.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2804:543c:8000::/34 | Valid | Other IRR onlyRADB | 636 100% |
| 2804:543c:c000::/34 | Valid | Other IRR onlyRADB | 636 100% |
| 2804:543c:8120::/45 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 2804:543c:8130::/45 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS268636'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 16 are in fix.csv.
- ROA: none2
- Route object: none4
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:543c::/34 | No ROA covers it. Add a ROA for AS268636, maxLength 34. |
| Route object: none | 2804:543c::/34 | No route object for it. A route object for 2804:543c::/32 with origin AS268636 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268636 in the RIR database for the space. |
| ROA: none | 38.210.62.0/24 | No ROA covers it. Add a ROA for AS268636, maxLength 24. |
| Route object: RIR | 38.210.62.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 45.164.181.0/24 | No route object for it. A route object for 45.164.180.0/22 with origin AS268636 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268636 in the RIR database for the space. |
| Route object: none | 45.164.180.0/24 | No route object for it. A route object for 45.164.180.0/22 with origin AS268636 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268636 in the RIR database for the space. |
| Route object: none | 2804:543c:4000::/34 | No route object for it. A route object for 2804:543c::/32 with origin AS268636 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268636 in the RIR database for the space. |
| Route object: RIR | 45.164.182.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.164.182.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.164.183.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:543c:8000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:543c:c000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:543c:8120::/45 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:543c:8130::/45 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268636 whose prefix no peer sees AS268636 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.164.180.0/22 | RADB, TC | No ROA |
| 2804:543c::/32 | RADB, 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.