bgpreport

Network · data from 2026-11-12

AS28296 Acessa Telecomunicações Ltda

Registry name: AS28296 - Acessa Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

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

170.81.172.0/23 No ROA Other origin only 6 1%low visibility 5
177.155.180.0/22 No ROA Other origin only 4 1%low visibility 3
189.36.216.0/21 No ROA Other IRR onlyALTDB, RADB 671 100% 66
189.36.221.0/24 No ROA Other IRR onlyTC 671 100% 66
2001:1298::/32 No ROA Other IRR onlyTC 339 53% 65
189.36.216.0/24 Valid Other IRR onlyTC 671 100% 66
189.36.223.0/24 Valid Other IRR onlyTC 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS28296: AS28296. 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 (AS28296 isn't in the set, or no route object for AS28296 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.

NameDatabaseASNsSets Route objectsAS28296 in itNot covered
AS28296 A single AS number, not a set: AS28296 (this network), 9 route objects.

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: none5
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none170.81.172.0/23No ROA covers it. Add a ROA for AS28296, maxLength 23.6 of 673
Route object: none170.81.172.0/23Route objects for it name AS264100. Add a route object with origin AS28296 in the RIR database for the space.6 of 673
ROA: none177.155.180.0/22No ROA covers it. Add a ROA for AS28296, maxLength 22.4 of 673
Route object: none177.155.180.0/22Route objects for it name AS264100. Add a route object with origin AS28296 in the RIR database for the space.4 of 673
ROA: none189.36.216.0/21No ROA covers it. Add a ROA for AS28296, maxLength 21.671 of 673
Route object: RIR189.36.216.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none189.36.221.0/24No ROA covers it. Add a ROA for AS28296, maxLength 24.671 of 673
Route object: RIR189.36.221.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none2001:1298::/32No ROA covers it. Add a ROA for AS28296, maxLength 32.339 of 636
Route object: RIR2001:1298::/32Route object only in TC. Add it in the RIR database for the space.339 of 636
Route object: RIR189.36.216.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR189.36.223.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

189.36.217.0/24TCNo ROA
189.36.218.0/24TCNo ROA
189.36.219.0/24TCNo ROA
189.36.220.0/24TCNo 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.