Network · data from 2026-11-12
AS268205 Rede Brasil Networks
Registry name: AS268205 - Rede Brasil Networks, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268205, 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.
| 38.7.224.0/19 | Invalid: origin | None | 5 1%low visibility |
| 177.74.176.0/24 | No ROA | None | 115 17% |
| 45.236.48.0/22 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 2804:4d90::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 45.236.48.0/24 | Valid | Other IRR onlyTC | 213 32% |
| 45.236.49.0/24 | Valid | Other IRR onlyTC | 213 32% |
| 45.236.50.0/24 | Valid | Other IRR onlyTC | 213 32% |
| 45.236.51.0/24 | Valid | Other IRR onlyTC | 213 32% |
AS-SET
PeeringDB's irr_as_set for AS268205: AS268205:RS-ROUTES. 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 (AS268205 isn't in the set, or no route object for AS268205 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 | AS268205 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS268205:RS-ROUTES | A route-set, not an AS-SET; route-sets aren't expanded. | |||||
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 10 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none2
- Route object: RIR6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 38.7.224.0/19 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS268205 should announce it, add a ROA for AS268205. |
| Route object: none | 38.7.224.0/19 | No route object for it. Add a route object with origin AS268205 in the RIR database for the space. |
| ROA: none | 177.74.176.0/24 | No ROA covers it. Add a ROA for AS268205, maxLength 24. |
| Route object: none | 177.74.176.0/24 | No route object for it. Add a route object with origin AS268205 in the RIR database for the space. |
| Route object: RIR | 45.236.48.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:4d90::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.236.48.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.236.49.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.236.50.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.236.51.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS268205 is announced.
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.