Network · data from 2026-11-12
AS268607 BCM SERVICOS DE COMUNICACAO E MULTIMIDIA
Registry name: AS268607 - BCM SERVICOS DE COMUNICACAO E MULTIMIDIA LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS268607, 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.
| 45.164.76.0/24 | No ROA | Nonecovered by 45.164.76.0/23 | 670 100% |
| 45.164.77.0/24 | No ROA | Nonecovered by 45.164.76.0/23 | 670 100% |
| 45.164.78.0/24 | No ROA | Nonecovered by 45.164.78.0/23 | 670 100% |
| 45.164.79.0/24 | No ROA | Nonecovered by 45.164.78.0/23 | 670 100% |
| 45.164.76.0/22 | No ROA | Other IRR onlyNTTCOM, RADB, TC | 670 100% |
| 2804:53cc::/32 | No ROA | Other IRR onlyNTTCOM, TC | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS268607: AS268607:AS-FIBRACONECTA. 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 (AS268607 isn't in the set, or no route object for AS268607 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 | AS268607 in it | Not covered |
|---|---|---|---|---|---|
| AS268607:AS-FIBRACONECTA | TC | 1 | 1 | 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 16 are in fix.csv.
- ROA: none6
- Route object: none4
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 45.164.76.0/24 | No ROA covers it. Add a ROA for AS268607, maxLength 24. |
| Route object: none | 45.164.76.0/24 | No route object for it. A route object for 45.164.76.0/23 with origin AS268607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268607 in the RIR database for the space. |
| ROA: none | 45.164.77.0/24 | No ROA covers it. Add a ROA for AS268607, maxLength 24. |
| Route object: none | 45.164.77.0/24 | No route object for it. A route object for 45.164.76.0/23 with origin AS268607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268607 in the RIR database for the space. |
| ROA: none | 45.164.78.0/24 | No ROA covers it. Add a ROA for AS268607, maxLength 24. |
| Route object: none | 45.164.78.0/24 | No route object for it. A route object for 45.164.78.0/23 with origin AS268607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268607 in the RIR database for the space. |
| ROA: none | 45.164.79.0/24 | No ROA covers it. Add a ROA for AS268607, maxLength 24. |
| Route object: none | 45.164.79.0/24 | No route object for it. A route object for 45.164.78.0/23 with origin AS268607 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268607 in the RIR database for the space. |
| ROA: none | 45.164.76.0/22 | No ROA covers it. Add a ROA for AS268607, maxLength 22. |
| Route object: RIR | 45.164.76.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:53cc::/32 | No ROA covers it. Add a ROA for AS268607, maxLength 32. |
| Route object: RIR | 2804:53cc::/32 | Route object only in NTTCOM, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS268607 whose prefix no peer sees AS268607 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.164.76.0/23 | RADB | No ROA |
| 45.164.78.0/23 | RADB | No ROA |
| 177.36.192.0/19 | NTTCOM | No ROA |
| 2804:3dc::/32 | NTTCOM | 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.