Network · data from 2026-11-12
AS273803 AS273803 - Tiago Coinaski - Me
Registry name: AS273803 - Tiago Coinaski - Me, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273803, 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.
| 177.73.132.0/24 | Invalid: origin | Nonecovered by 177.73.132.0/22 | 2 0%low visibility |
| 177.73.133.0/24 | Invalid: origin | Nonecovered by 177.73.132.0/22 | 2 0%low visibility |
| 177.73.132.0/23 | Invalid: origin | Nonecovered by 177.73.132.0/22 | 0 0%low visibility |
| 177.73.134.0/23 | Invalid: origin | Other origin onlycovered by 177.73.132.0/22 | 0 0%low visibility |
| 177.73.134.0/24 | Invalid: origin | Other origin onlycovered by 177.73.132.0/22 | 0 0%low visibility |
| 177.73.135.0/24 | Invalid: origin | Other origin onlycovered by 177.73.132.0/22 | 0 0%low visibility |
AS-SET
AS273803 isn't in PeeringDB, where networks name their AS-SET.
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: origin6
- Route object: none6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 177.73.132.0/24 | ROAs covering it name AS273525, not AS273803. If AS273803 should announce it, add a ROA for AS273803. |
| Route object: none | 177.73.132.0/24 | No route object for it. A route object for 177.73.132.0/22 with origin AS273803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273803 in the RIR database for the space. |
| ROA: origin | 177.73.133.0/24 | ROAs covering it name AS273525, not AS273803. If AS273803 should announce it, add a ROA for AS273803. |
| Route object: none | 177.73.133.0/24 | No route object for it. A route object for 177.73.132.0/22 with origin AS273803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273803 in the RIR database for the space. |
| ROA: origin | 177.73.132.0/23 | ROAs covering it name AS273525, not AS273803. If AS273803 should announce it, add a ROA for AS273803. |
| Route object: none | 177.73.132.0/23 | No route object for it. A route object for 177.73.132.0/22 with origin AS273803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273803 in the RIR database for the space. |
| ROA: origin | 177.73.134.0/23 | ROAs covering it name AS274650, not AS273803. If AS273803 should announce it, add a ROA for AS273803. |
| Route object: none | 177.73.134.0/23 | Route objects for it name AS274650. A route object for 177.73.132.0/22 with origin AS273803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273803 in the RIR database for the space. |
| ROA: origin | 177.73.134.0/24 | ROAs covering it name AS274650, not AS273803. If AS273803 should announce it, add a ROA for AS273803. |
| Route object: none | 177.73.134.0/24 | Route objects for it name AS274650. A route object for 177.73.132.0/22 with origin AS273803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273803 in the RIR database for the space. |
| ROA: origin | 177.73.135.0/24 | ROAs covering it name AS274650, not AS273803. If AS273803 should announce it, add a ROA for AS273803. |
| Route object: none | 177.73.135.0/24 | Route objects for it name AS274650. A route object for 177.73.132.0/22 with origin AS273803 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273803 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS273803 whose prefix no peer sees AS273803 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.73.132.0/22 | RADB | No ROA |
| 2804:8c74::/32 | RADB | No ROA |
| 2804:8c74::/33 | RADB | No ROA |
| 2804:8c74:8000::/33 | 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.