bgpreport

Network · data from 2026-11-12

AS268390 ALISSON HENRIQUE DUARTE SERVICOS

Registry name: AS268390 - ALISSON HENRIQUE DUARTE SERVICOS - ME, BR · PeeringDB

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

Announced routes

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

45.239.239.0/24 No ROA Other IRR onlyRADB 672 100% 67
45.239.238.0/24 No ROA Other IRR onlyRADB 670 100% 66
45.239.236.0/23 No ROA Other IRR onlyRADB 669 99% 67
2804:5074::/33 No ROA Other IRR onlyRADB 636 100% 67
2804:5074:8000::/34 No ROA Other IRR onlyRADB 632 99% 67
45.239.236.0/24 No ROA Other IRR onlyRADB 127 19% 44
45.239.237.0/24 No ROA Other IRR onlyRADB 127 19% 44

AS-SET

PeeringDB's irr_as_set for AS268390: AS268390. 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 (AS268390 isn't in the set, or no route object for AS268390 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 objectsAS268390 in itNot covered
AS268390 A single AS number, not a set: AS268390 (this network), 10 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 17 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none45.239.239.0/24No ROA covers it. Add a ROA for AS268390, maxLength 24.672 of 673
Route object: RIR45.239.239.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.239.238.0/24No ROA covers it. Add a ROA for AS268390, maxLength 24.670 of 673
Route object: RIR45.239.238.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.239.236.0/23No ROA covers it. Add a ROA for AS268390, maxLength 23.669 of 673
Route object: RIR45.239.236.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:5074::/33No ROA covers it. Add a ROA for AS268390, maxLength 33.636 of 636
Route object: RIR2804:5074::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:5074:8000::/34No ROA covers it. Add a ROA for AS268390, maxLength 34.632 of 636
Route object: RIR2804:5074:8000::/34Route object only in RADB. Add it in the RIR database for the space.632 of 636
ROA: none45.239.236.0/24No ROA covers it. Add a ROA for AS268390, maxLength 24.127 of 673
Route object: RIR45.239.236.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673
ROA: none45.239.237.0/24No ROA covers it. Add a ROA for AS268390, maxLength 24.127 of 673
Route object: RIR45.239.237.0/24Route object only in RADB. Add it in the RIR database for the space.127 of 673

Route objects not announced

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

45.239.236.0/22RADB, TCNo ROA
45.239.238.0/23RADBNo ROA
2804:5074::/32RADB, TCNo 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.