Network · data from 2026-11-12
AS61923 SUNWAY TELECOM
Registry name: AS61923 - SUNWAY TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61923, 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.
| 200.7.112.0/20 | Valid | Other IRR onlyTC | 670 100% |
| 2804:1834::/32 | Valid | Other IRR onlyTC | 633 100% |
| 200.7.112.0/23 | Valid | Other IRR onlyTC | 206 31% |
| 200.7.114.0/23 | Valid | Other IRR onlyTC | 206 31% |
| 200.7.118.0/23 | Valid | Other IRR onlyTC | 206 31% |
| 200.7.122.0/23 | Valid | Other IRR onlyTC | 206 31% |
| 200.7.116.0/23 | Valid | Other IRR onlyTC | 205 30% |
| 200.7.120.0/23 | Valid | Other IRR onlyTC | 205 30% |
| 200.7.124.0/23 | Valid | Other IRR onlyTC | 205 30% |
| 200.7.126.0/23 | Valid | Other IRR onlyTC | 205 30% |
| 200.7.112.0/24 | Valid | Other IRR onlyTC | 2 0%low visibility |
| 200.7.113.0/24 | Valid | Other IRR onlyTC | 2 0%low visibility |
| 108.186.252.0/24 | Valid | RIR databaseARIN, RADB | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS61923: AS61923:AS-ANUNCIOS. 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 (AS61923 isn't in the set, or no route object for AS61923 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 | AS61923 in it | Not covered |
|---|---|---|---|---|---|
| AS61923:AS-ANUNCIOS | TClists itself further down2 member sets in no database: AS-BRASILANTENAS-ALL, AS-FORTLINKTELECOM-ALL | 28 | 4 | 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 34 are in fix.csv.
- Route object: RIR12
- AS-SET: missing member2
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 200.7.112.0/20 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1834::/32 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.112.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.114.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.118.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.122.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.116.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.120.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.124.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.126.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.112.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.7.113.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: missing member | AS61923:AS-ANUNCIOS | AS61923:AS-ANUNCIOS (TC) lists AS-BRASILANTENAS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS61923:AS-ANUNCIOS | AS61923:AS-ANUNCIOS (TC) lists AS-FORTLINKTELECOM-ALL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS61923 whose prefix no peer sees AS61923 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.7.112.0/21 | TC | Valid |
| 200.7.112.0/22 | TC | Valid |
| 200.7.114.0/24 | TC | Valid |
| 200.7.115.0/24 | TC | Valid |
| 200.7.116.0/22 | TC | Valid |
| 200.7.116.0/24 | TC | Valid |
| 200.7.117.0/24 | TC | Valid |
| 200.7.118.0/24 | TC | Valid |
| 200.7.119.0/24 | TC | Valid |
| 200.7.120.0/21 | TC | Valid |
| 200.7.120.0/22 | TC | Valid |
| 200.7.120.0/24 | TC | Valid |
| 200.7.121.0/24 | TC | Valid |
| 200.7.122.0/24 | TC | Valid |
| 200.7.123.0/24 | TC | Valid |
| 200.7.124.0/22 | TC | Valid |
| 200.7.124.0/24 | TC | Valid |
| 200.7.125.0/24 | TC | Valid |
| 200.7.126.0/24 | TC | Valid |
| 200.7.127.0/24 | 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.