bgpreport

Network · data from 2026-11-12

AS266468 ACESSANET TELECON

Registry name: AS266468 - ACESSANET TELECON LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266468, 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.83.144.0/23 No ROA Nonecovered by 170.83.144.0/22 668 99% 67
170.83.146.0/23 No ROA Nonecovered by 170.83.144.0/22 668 99% 67
2804:384c::/33 No ROA Nonecovered by 2804:384c::/32 352 55% 65
2804:384c:8000::/33 No ROA Nonecovered by 2804:384c::/32 352 55% 65
170.83.144.0/22 No ROA Other IRR onlyNTTCOM, RADB, TC 668 99% 67
2804:384c::/32 No ROA Other IRR onlyNTTCOM, RADB 630 99% 67
170.83.144.0/24 No ROA Other IRR onlyTC 206 31% 56
170.83.145.0/24 No ROA Other IRR onlyTC 206 31% 56
170.83.146.0/24 No ROA Other IRR onlyTC 206 31% 56
170.83.147.0/24 No ROA Other IRR onlyTC 206 31% 56

AS-SET

PeeringDB's irr_as_set for AS266468: AS-ACESSANET. 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 (AS266468 isn't in the set, or no route object for AS266468 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 objectsAS266468 in itNot covered
AS-ACESSANET TC 010 No 10

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

  • ROA: none10
  • Route object: none4
  • Route object: RIR6
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none170.83.144.0/23No ROA covers it. Add a ROA for AS266468, maxLength 23.668 of 673
Route object: none170.83.144.0/23No route object for it. A route object for 170.83.144.0/22 with origin AS266468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266468 in the RIR database for the space.668 of 673
ROA: none170.83.146.0/23No ROA covers it. Add a ROA for AS266468, maxLength 23.668 of 673
Route object: none170.83.146.0/23No route object for it. A route object for 170.83.144.0/22 with origin AS266468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266468 in the RIR database for the space.668 of 673
ROA: none2804:384c::/33No ROA covers it. Add a ROA for AS266468, maxLength 33.352 of 636
Route object: none2804:384c::/33No route object for it. A route object for 2804:384c::/32 with origin AS266468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266468 in the RIR database for the space.352 of 636
ROA: none2804:384c:8000::/33No ROA covers it. Add a ROA for AS266468, maxLength 33.352 of 636
Route object: none2804:384c:8000::/33No route object for it. A route object for 2804:384c::/32 with origin AS266468 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266468 in the RIR database for the space.352 of 636
ROA: none170.83.144.0/22No ROA covers it. Add a ROA for AS266468, maxLength 22.668 of 673
Route object: RIR170.83.144.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:384c::/32No ROA covers it. Add a ROA for AS266468, maxLength 32.630 of 636
Route object: RIR2804:384c::/32Route object only in NTTCOM, RADB. Add it in the RIR database for the space.630 of 636
ROA: none170.83.144.0/24No ROA covers it. Add a ROA for AS266468, maxLength 24.206 of 673
Route object: RIR170.83.144.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
ROA: none170.83.145.0/24No ROA covers it. Add a ROA for AS266468, maxLength 24.206 of 673
Route object: RIR170.83.145.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
ROA: none170.83.146.0/24No ROA covers it. Add a ROA for AS266468, maxLength 24.206 of 673
Route object: RIR170.83.146.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
ROA: none170.83.147.0/24No ROA covers it. Add a ROA for AS266468, maxLength 24.206 of 673
Route object: RIR170.83.147.0/24Route object only in TC. Add it in the RIR database for the space.206 of 673
AS-SET: own ASNAS-ACESSANETAS266468 isn't in AS-ACESSANET (TC) once expanded. Add AS266468 to it.

Route objects not announced

Every route object with origin AS266468 is announced.

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.