Network · data from 2026-11-12
AS266121 A.S.DOS SANTOS - TECNOLOGIA DA INFORMACAO
Registry name: AS266121 - SUPER SONIC TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266121, 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.
| 187.49.184.0/22 | Invalid: origin | Other origin only | 1 0%low visibility |
| 187.49.184.0/23 | Invalid: origin | None | 1 0%low visibility |
| 187.49.186.0/23 | Invalid: origin | None | 1 0%low visibility |
| 2804:3af8::/33 | Valid | Nonecovered by 2804:3af8::/32 | 635 100% |
| 2804:3af8:8000::/33 | Valid | Nonecovered by 2804:3af8::/32 | 635 100% |
| 2804:3af8::/34 | Valid | Nonecovered by 2804:3af8::/32 | 352 55% |
| 2804:3af8:8000::/34 | Valid | Nonecovered by 2804:3af8::/32 | 352 55% |
| 2804:3af8::/35 | Valid | Nonecovered by 2804:3af8::/32 | 1 0%low visibility |
| 2804:3af8:8000::/35 | Valid | Nonecovered by 2804:3af8::/32 | 1 0%low visibility |
| 45.6.28.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 671 100% |
| 45.6.30.0/23 | Valid | Other IRR onlyALTDB | 671 100% |
| 45.6.28.0/23 | Valid | Other IRR onlyALTDB | 670 100% |
| 2804:3af8::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 635 100% |
| 45.6.28.0/24 | Valid | Other IRR onlyALTDB | 206 31% |
| 45.6.31.0/24 | Valid | Other IRR onlyALTDB | 206 31% |
| 45.6.29.0/24 | Valid | Other IRR onlyALTDB | 205 30% |
| 45.6.30.0/24 | Valid | Other IRR onlyALTDB | 205 30% |
AS-SET
PeeringDB's irr_as_set for AS266121: AS-266121. 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 (AS266121 isn't in the set, or no route object for AS266121 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 | AS266121 in it | Not covered |
|---|---|---|---|---|---|
| AS-266121 | ALTDB | 9 | 2 | Yes | 3 |
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 21 are in fix.csv.
- ROA: origin3
- Route object: none9
- Route object: RIR8
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 187.49.184.0/22 | ROAs covering it name AS270512, not AS266121. If AS266121 should announce it, add a ROA for AS266121. |
| Route object: none | 187.49.184.0/22 | Route objects for it name AS270512. Add a route object with origin AS266121 in the RIR database for the space. |
| ROA: origin | 187.49.184.0/23 | ROAs covering it name AS270512, not AS266121. If AS266121 should announce it, add a ROA for AS266121. |
| Route object: none | 187.49.184.0/23 | No route object for it. Add a route object with origin AS266121 in the RIR database for the space. |
| ROA: origin | 187.49.186.0/23 | ROAs covering it name AS270512, not AS266121. If AS266121 should announce it, add a ROA for AS266121. |
| Route object: none | 187.49.186.0/23 | No route object for it. Add a route object with origin AS266121 in the RIR database for the space. |
| Route object: none | 2804:3af8::/33 | No route object for it. A route object for 2804:3af8::/32 with origin AS266121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266121 in the RIR database for the space. |
| Route object: none | 2804:3af8:8000::/33 | No route object for it. A route object for 2804:3af8::/32 with origin AS266121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266121 in the RIR database for the space. |
| Route object: none | 2804:3af8::/34 | No route object for it. A route object for 2804:3af8::/32 with origin AS266121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266121 in the RIR database for the space. |
| Route object: none | 2804:3af8:8000::/34 | No route object for it. A route object for 2804:3af8::/32 with origin AS266121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266121 in the RIR database for the space. |
| Route object: none | 2804:3af8::/35 | No route object for it. A route object for 2804:3af8::/32 with origin AS266121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266121 in the RIR database for the space. |
| Route object: none | 2804:3af8:8000::/35 | No route object for it. A route object for 2804:3af8::/32 with origin AS266121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266121 in the RIR database for the space. |
| Route object: RIR | 45.6.28.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.30.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.28.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3af8::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.28.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.31.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.29.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 45.6.30.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266121 whose prefix no peer sees AS266121 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:448c::/32 | 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.