Network · data from 2026-11-12
AS270311 BSB Link Fibra
Registry name: AS270311 - BSB Link Fibra, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270311, 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.
| 189.113.188.0/24 | Valid | Nonecovered by 189.113.188.0/22 | 671 100% |
| 189.113.190.0/24 | Valid | Nonecovered by 189.113.188.0/22 | 671 100% |
| 189.113.191.0/24 | Valid | Nonecovered by 189.113.188.0/22 | 671 100% |
| 189.113.189.0/24 | Valid | Nonecovered by 189.113.188.0/22 | 670 100% |
| 2804:6a20::/35 | Valid | Nonecovered by 2804:6a20::/32 | 635 100% |
| 2804:6a20:4000::/35 | Valid | Nonecovered by 2804:6a20::/32 | 635 100% |
| 2804:6a20:a000::/35 | Valid | Nonecovered by 2804:6a20::/32 | 635 100% |
| 2804:6a20:e000::/35 | Valid | Nonecovered by 2804:6a20::/32 | 635 100% |
| 2804:6a20:2000::/35 | Valid | Nonecovered by 2804:6a20::/32 | 1 0%low visibility |
AS-SET
AS270311'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 11 are in fix.csv.
- Route object: none9
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 189.113.188.0/24 | No route object for it. A route object for 189.113.188.0/22 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 189.113.190.0/24 | No route object for it. A route object for 189.113.188.0/22 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 189.113.191.0/24 | No route object for it. A route object for 189.113.188.0/22 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 189.113.189.0/24 | No route object for it. A route object for 189.113.188.0/22 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 2804:6a20::/35 | No route object for it. A route object for 2804:6a20::/32 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 2804:6a20:4000::/35 | No route object for it. A route object for 2804:6a20::/32 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 2804:6a20:a000::/35 | No route object for it. A route object for 2804:6a20::/32 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 2804:6a20:e000::/35 | No route object for it. A route object for 2804:6a20::/32 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
| Route object: none | 2804:6a20:2000::/35 | No route object for it. A route object for 2804:6a20::/32 with origin AS270311 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270311 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270311 whose prefix no peer sees AS270311 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 189.113.188.0/22 | ALTDB, RADB, TC | Valid |
| 2804:6a20::/32 | ALTDB, RADB, TC | 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.