bgpreport

Network · data from 2026-11-12

AS270899 AS270899 - Worksul Telecom

Registry name: AS270899 - Worksul Telecom, BR · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 routes 50.0% RPKI valid · 50.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
0No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS270899, seen from no peer

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 19
2804:7328:8000::/33 Invalid: maxLength Nonecovered by 2804:7328::/32 39 6%low visibility 19
177.91.228.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 67
177.91.228.0/23 Valid Other IRR onlyRADB 672 100% 67
177.91.231.0/24 Valid Other IRR onlyRADB 672 100% 67
2804:7328::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:7328:2000::/36 Valid Other IRR onlyRADB 635 100% 67
177.91.228.0/24 Valid Other IRR onlyRADB 2 0%low visibility 3

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
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:7328::/33ROA 2804:7328::/32 AS270899 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:7328::/33.39 of 636
Route object: none2804:7328::/33No 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.39 of 636
ROA: maxLength2804:7328:8000::/33ROA 2804:7328::/32 AS270899 has maxLength 32; the route is a /33. Raise the maxLength, or add a ROA for 2804:7328:8000::/33.39 of 636
Route object: none2804:7328:8000::/33No 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.39 of 636
Route object: RIR177.91.228.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.228.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.91.231.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:7328::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:7328:2000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR177.91.228.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673

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/24RADBValid
177.91.230.0/24RADBValid
2804:7328:1000::/36RADBValid

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.