Network · data from 2026-11-12
AS275674 A S GOMES TELECOM
Registry name: AS275674 - A S GOMES TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS275674, 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:9830::/34 | Valid | Nonecovered by 2804:9830::/33 | 1 0%low visibility |
| 2804:9830:4000::/34 | Valid | Nonecovered by 2804:9830::/33 | 1 0%low visibility |
| 2804:9830:8000::/34 | Valid | Nonecovered by 2804:9830:8000::/33 | 1 0%low visibility |
| 2804:9830:c000::/34 | Valid | Nonecovered by 2804:9830:8000::/33 | 1 0%low visibility |
| 45.227.46.0/24 | Valid | Other IRR onlyTC | 670 100% |
| 2804:9830::/32 | Valid | Other IRR onlyRADB, TC | 631 99% |
| 2804:9830::/33 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 2804:9830:8000::/33 | Valid | Other IRR onlyTC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS275674: AS275674:AS-ASGOMES. 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 (AS275674 isn't in the set, or no route object for AS275674 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 | AS275674 in it | Not covered |
|---|---|---|---|---|---|
| AS275674:AS-ASGOMES | TC | 1 | 3 | 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 8 are in fix.csv.
- Route object: none4
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:9830::/34 | No route object for it. A route object for 2804:9830::/33 with origin AS275674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275674 in the RIR database for the space. |
| Route object: none | 2804:9830:4000::/34 | No route object for it. A route object for 2804:9830::/33 with origin AS275674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275674 in the RIR database for the space. |
| Route object: none | 2804:9830:8000::/34 | No route object for it. A route object for 2804:9830:8000::/33 with origin AS275674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275674 in the RIR database for the space. |
| Route object: none | 2804:9830:c000::/34 | No route object for it. A route object for 2804:9830:8000::/33 with origin AS275674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275674 in the RIR database for the space. |
| Route object: RIR | 45.227.46.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9830::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9830::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9830:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS275674 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.