bgpreport

Network · data from 2026-11-12

AS266444 3L CLOUD INTERNET SERVICES

Registry name: AS266444 - 3L CLOUD INTERNET SERVICES LTDA - EPP, BR · PeeringDB

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

Announced routes

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

38.224.134.0/24 No ROA Other IRR onlyRADB 665 99% 67
170.82.172.0/22 Valid Other IRR onlyRADB 670 100% 67
170.82.172.0/23 Valid Other IRR onlyRADB 670 100% 67
170.82.172.0/24 Valid Other IRR onlyRADB 670 100% 67
170.82.174.0/23 Valid Other IRR onlyRADB 670 100% 67
170.82.175.0/24 Valid Other IRR onlyRADB 670 100% 67
2804:37ec::/42 Valid Other IRR onlyRADB 634 100% 67
2804:37ec:100::/42 Valid Other IRR onlyRADB 634 100% 67
2804:37ec:1000::/42 Valid Other IRR onlyRADB 634 100% 67
2804:37ec:1100::/42 Valid Other IRR onlyRADB 634 100% 67
2804:37ec:4000::/46 Valid Other IRR onlyRADB 634 100% 67
2804:37ec:4004::/46 Valid Other IRR onlyRADB 634 100% 67
2804:37ec:4008::/46 Valid Other IRR onlyRADB 630 99% 67
170.82.173.0/24 Valid Other IRR onlyRADB 71 11% 26
170.82.174.0/24 Valid Other IRR onlyRADB 71 11% 26
2804:37ec::/44 Valid Other IRR onlyRADB 64 10% 26
2804:37ec:100::/44 Valid Other IRR onlyRADB 64 10% 26
2804:37ec:1000::/44 Valid Other IRR onlyRADB 64 10% 26
2804:37ec:1100::/44 Valid Other IRR onlyRADB 64 10% 26

AS-SET

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

  • ROA: none1
  • Route object: RIR19
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: none38.224.134.0/24No ROA covers it. Add a ROA for AS266444, maxLength 24.665 of 673
Route object: RIR38.224.134.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR170.82.172.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR170.82.172.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR170.82.172.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR170.82.174.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR170.82.175.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:37ec::/42Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:37ec:100::/42Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:37ec:1000::/42Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:37ec:1100::/42Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:37ec:4000::/46Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:37ec:4004::/46Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:37ec:4008::/46Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR170.82.173.0/24Route object only in RADB. Add it in the RIR database for the space.71 of 673
Route object: RIR170.82.174.0/24Route object only in RADB. Add it in the RIR database for the space.71 of 673
Route object: RIR2804:37ec::/44Route object only in RADB. Add it in the RIR database for the space.64 of 636
Route object: RIR2804:37ec:100::/44Route object only in RADB. Add it in the RIR database for the space.64 of 636
Route object: RIR2804:37ec:1000::/44Route object only in RADB. Add it in the RIR database for the space.64 of 636
Route object: RIR2804:37ec:1100::/44Route object only in RADB. Add it in the RIR database for the space.64 of 636

Route objects not announced

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

2804:37ec::/40RADBValid
2804:37ec::/48RADBValid
2804:37ec:100::/40RADBValid
2804:37ec:100::/48RADBValid
2804:37ec:1000::/40RADBValid
2804:37ec:1000::/48RADBValid
2804:37ec:1100::/40RADBValid
2804:37ec:1100::/48RADBValid
2804:37ec:4000::/48RADBValid
2804:37ec:4004::/48RADBValid
2804:37ec:4008::/48RADBValid

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.