bgpreport

Network · data from 2026-11-12

AS28274 AS28274 - ENTERPRISE SERVICES BRASIL SERVICOS DE TECNOLOGIA

Registry name: AS28274 - ENTERPRISE SERVICES BRASIL SERVICOS DE TECNOLOGIA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28274, 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.

201.33.128.0/20 No ROA Other IRR onlyRADB 672 100% 66
201.33.128.0/21 No ROA Other IRR onlyRADB 672 100% 66
201.33.136.0/21 No ROA Other IRR onlyRADB 672 100% 66
2607:f028:38::/48 Valid RIR databaseARIN, RADB 634 100% 67

AS-SET

AS28274 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 22 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none201.33.128.0/20No ROA covers it. Add a ROA for AS28274, maxLength 20.672 of 673
Route object: RIR201.33.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none201.33.128.0/21No ROA covers it. Add a ROA for AS28274, maxLength 21.672 of 673
Route object: RIR201.33.128.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none201.33.136.0/21No ROA covers it. Add a ROA for AS28274, maxLength 21.672 of 673
Route object: RIR201.33.136.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS28274 whose prefix no peer sees AS28274 announce. Many are kept on purpose (backup routes, space announced only in some places).

201.33.128.0/24RADBNo ROA
201.33.129.0/24RADBNo ROA
201.33.130.0/24RADBNo ROA
201.33.131.0/24RADBNo ROA
201.33.132.0/24RADBNo ROA
201.33.133.0/24RADBNo ROA
201.33.136.0/24RADBNo ROA
201.33.137.0/24RADBNo ROA
201.33.138.0/24RADBNo ROA
201.33.139.0/24RADBNo ROA
201.33.140.0/24RADBNo ROA
201.33.141.0/24RADBNo ROA
201.33.142.0/24RADBNo ROA
201.33.143.0/24RADBNo ROA
2804:1c00::/32RADBNo ROA
2804:1c00::/48RADBNo 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.