Network · data from 2026-11-12
AS270899 AS270899 - Worksul Telecom
Registry name: AS270899 - Worksul Telecom, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270899, 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:7328::/33 | Invalid: maxLength | Nonecovered by 2804:7328::/32 | 39 6%low visibility |
| 2804:7328:8000::/33 | Invalid: maxLength | Nonecovered by 2804:7328::/32 | 39 6%low visibility |
| 177.91.228.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 177.91.228.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 177.91.231.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2804:7328::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2804:7328:2000::/36 | Valid | Other IRR onlyRADB | 635 100% |
| 177.91.228.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
AS270899 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 13 are in fix.csv.
- ROA: maxLength2
- Route object: none2
- Route object: RIR6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2804:7328::/33 | ROA 2804:7328::/32 AS270899 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:7328::/33. |
| Route object: none | 2804:7328::/33 | No route object for it. A route object for 2804:7328::/32 with origin AS270899 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270899 in the RIR database for the space. |
| ROA: maxLength | 2804:7328:8000::/33 | ROA 2804:7328::/32 AS270899 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:7328:8000::/33. |
| Route object: none | 2804:7328:8000::/33 | No route object for it. A route object for 2804:7328::/32 with origin AS270899 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270899 in the RIR database for the space. |
| Route object: RIR | 177.91.228.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.228.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.231.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7328::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7328:2000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.228.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270899 whose prefix no peer sees AS270899 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.91.229.0/24 | RADB | Valid |
| 177.91.230.0/24 | RADB | Valid |
| 2804:7328:1000::/36 | RADB | 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.