Network · data from 2026-11-12
AS269506 BRLOGNET TELECOMUNICACOES LTDA
Registry name: AS269506 - BRLOGNET TELECOMUNICACOES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269506, 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:65a8:1200::/40 | Valid | Nonecovered by 2804:65a8::/32 | 366 58% |
| 2804:65a8:1300::/40 | Valid | Nonecovered by 2804:65a8::/32 | 366 58% |
| 2804:65a8::/33 | Valid | Nonecovered by 2804:65a8::/32 | 61 10%low visibility |
| 45.170.176.0/22 | Valid | Other IRR onlyALTDB | 672 100% |
| 45.187.224.0/22 | Valid | Other IRR onlyALTDB | 672 100% |
| 2804:65a8::/32 | Valid | Other IRR onlyALTDB | 634 100% |
| 2804:65a8:1000::/40 | Valid | Other IRR onlyALTDB | 366 58% |
| 2804:65a8:1100::/40 | Valid | Other IRR onlyALTDB | 366 58% |
| 45.170.176.0/24 | Valid | Other IRR onlyALTDB | 243 36% |
| 45.170.177.0/24 | Valid | Other IRR onlyALTDB | 243 36% |
| 45.170.178.0/24 | Valid | Other IRR onlyALTDB | 243 36% |
| 45.170.179.0/24 | Valid | Other IRR onlyALTDB | 243 36% |
| 45.187.225.0/24 | Valid | Other IRR onlyALTDB | 243 36% |
| 45.187.226.0/24 | Valid | Other IRR onlyALTDB | 243 36% |
| 45.187.227.0/24 | Valid | Other IRR onlyALTDB | 243 36% |
| 45.187.224.0/24 | Valid | Other IRR onlyALTDB | 242 36% |
| 45.170.176.0/23 | Valid | Other IRR onlyALTDB | 200 30% |
| 45.170.178.0/23 | Valid | Other IRR onlyALTDB | 200 30% |
| 45.187.224.0/23 | Valid | Other IRR onlyALTDB | 200 30% |
| 45.187.226.0/23 | Valid | Other IRR onlyALTDB | 200 30% |
| 38.210.232.0/22 | Valid | RIR databaseARIN | 672 100% |
| 38.210.232.0/24 | Valid | RIR databaseARIN | 243 36% |
| 38.210.233.0/24 | Valid | RIR databaseARIN | 243 36% |
| 38.210.235.0/24 | Valid | RIR databaseARIN | 243 36% |
| 38.210.234.0/24 | Valid | RIR databaseARIN | 242 36% |
AS-SET
PeeringDB's irr_as_set for AS269506: AS269506:AS-ALL. 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 (AS269506 isn't in the set, or no route object for AS269506 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 | AS269506 in it | Not covered |
|---|---|---|---|---|---|
| AS269506:AS-ALL | ALTDBlists itself further down | 11 | 10 | Yes | 0 |
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 22 are in fix.csv.
- Route object: none3
- Route object: RIR17
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:65a8:1200::/40 | No route object for it. A route object for 2804:65a8::/32 with origin AS269506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269506 in the RIR database for the space. |
| Route object: none | 2804:65a8:1300::/40 | No route object for it. A route object for 2804:65a8::/32 with origin AS269506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269506 in the RIR database for the space. |
| Route object: none | 2804:65a8::/33 | No route object for it. A route object for 2804:65a8::/32 with origin AS269506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269506 in the RIR database for the space. |
| Route object: RIR | 45.170.176.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.224.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:65a8::/32 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:65a8:1000::/40 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:65a8:1100::/40 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.170.176.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.170.177.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.170.178.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.170.179.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.225.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.226.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.227.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.224.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.170.176.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.170.178.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.224.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.226.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269506 whose prefix no peer sees AS269506 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.210.232.0/23 | ARIN | Valid |
| 38.210.234.0/23 | ARIN | 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.