bgpreport

Network · data from 2026-11-12

AS266060 DIGIL 360 PROVEDORES DE ACESSO

Registry name: AS266060 - DIGIL 360 PROVEDORES DE ACESSO LTDA-ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266060, 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.4.225.0/24 No ROA Nonecovered by 45.4.224.0/23 664 99% 67
45.4.224.0/24 No ROA Other IRR onlyRADB 664 99% 67
45.4.224.0/23 No ROA Other IRR onlyALTDB 660 98% 67
2804:39f0::/32 No ROA Other IRR onlyNTTCOM, RADB, TC 629 99% 67
45.4.226.0/24 Valid Nonecovered by 45.4.224.0/22 667 99% 67
45.4.227.0/24 Valid Other IRR onlyRADB 664 99% 66
2804:39f0:f000::/40 Valid Other IRR onlyALTDB, RADB 631 99% 67
2804:39f0:f100::/40 Valid Other IRR onlyRADB 631 99% 69
2804:39f0:f100::/41 Valid Other IRR onlyRADB 631 99% 69
2804:39f0:f180::/41 Valid Other IRR onlyRADB 631 99% 69

AS-SET

PeeringDB's irr_as_set for AS266060: AS266060. 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 (AS266060 isn't in the set, or no route object for AS266060 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 objectsAS266060 in itNot covered
AS266060 A single AS number, not a set: AS266060 (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 16 are in fix.csv.

  • ROA: none4
  • Route object: none2
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.4.225.0/24No ROA covers it. Add a ROA for AS266060, maxLength 24.664 of 673
Route object: none45.4.225.0/24No route object for it. A route object for 45.4.224.0/23 with origin AS266060 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266060 in the RIR database for the space.664 of 673
ROA: none45.4.224.0/24No ROA covers it. Add a ROA for AS266060, maxLength 24.664 of 673
Route object: RIR45.4.224.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none45.4.224.0/23No ROA covers it. Add a ROA for AS266060, maxLength 23.660 of 673
Route object: RIR45.4.224.0/23Route object only in ALTDB. Add it in the RIR database for the space.660 of 673
ROA: none2804:39f0::/32No ROA covers it. Add a ROA for AS266060, maxLength 32.629 of 636
Route object: RIR2804:39f0::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: none45.4.226.0/24No route object for it. A route object for 45.4.224.0/22 with origin AS266060 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266060 in the RIR database for the space.667 of 673
Route object: RIR45.4.227.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:39f0:f000::/40Route object only in ALTDB, RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:39f0:f100::/40Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:39f0:f100::/41Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:39f0:f180::/41Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

45.4.224.0/22NTTCOM, RADB, TCNo ROA
2804:39f0::/34ALTDBNo 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.