Network · data from 2026-11-12
AS270506 G5 Rede de Telecomunicacoes Multimidia
Registry name: AS270506 - G5 Rede de Telecomunicacoes Multimidia Ltda, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270506, 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.
| 186.0.150.0/24 | Valid | Nonecovered by 186.0.150.0/23 | 669 99% |
| 186.0.148.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 186.0.151.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2804:6d00::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 636 100% |
| 2804:6d00::/33 | Valid | Other IRR onlyRADB | 636 100% |
| 2804:6d00:8000::/33 | Valid | Other IRR onlyRADB | 636 100% |
| 2804:6d00::/34 | Valid | Other IRR onlyRADB | 634 100% |
| 2804:6d00:4000::/34 | Valid | Other IRR onlyRADB | 634 100% |
| 2804:6d00:8000::/34 | Valid | Other IRR onlyRADB | 634 100% |
| 2804:6d00:c000::/34 | Valid | Other IRR onlyRADB | 634 100% |
| 186.0.148.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS270506: AS270506:AS-G5TELECOM. 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 (AS270506 isn't in the set, or no route object for AS270506 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 | AS270506 in it | Not covered |
|---|---|---|---|---|---|
| AS270506:AS-G5TELECOM | ALTDB | 0 | 1 | No | 11 |
| TC (also) | 0 | 1 | No | 11 |
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 14 are in fix.csv.
- Route object: none1
- Route object: RIR10
- AS-SET: own ASN1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.0.150.0/24 | No route object for it. A route object for 186.0.150.0/23 with origin AS270506 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270506 in the RIR database for the space. |
| Route object: RIR | 186.0.148.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.0.151.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d00::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d00::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d00:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d00::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d00:4000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d00:8000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d00:c000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.0.148.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS270506:AS-G5TELECOM | AS270506 isn't in AS270506:AS-G5TELECOM (ALTDB) once expanded. Add AS270506 to it. |
Route objects not announced
Route objects with origin AS270506 whose prefix no peer sees AS270506 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 186.0.148.0/22 | ALTDB, RADB, TC | No ROA |
| 186.0.150.0/23 | RADB | 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.