Network · data from 2026-11-12
AS64072 EVOLUTION NET
Registry name: EVOLUTIONNET-BD - EVOLUTION NET (Internet Service Provider), BD · PeeringDB
8IPv4 routes
100.0% RPKI valid · 100.0% with a route object
29IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
0 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
64Route objects not announced
registered with origin AS64072, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS64072, 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.
| 103.25.120.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.25.121.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.25.122.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 165.101.79.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.25.123.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.69.77.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 160.250.69.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 165.101.78.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2404:bc80:c000::/34 | Valid | RIR databaseAPNIC | 636 100% |
| 2404:bc80::/33 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80::/34 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:4000::/34 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:8000::/33 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:8000::/34 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9000::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9004::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9008::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:900c::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9010::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9014::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9018::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:901c::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9020::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:9024::/46 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:bc80:1000::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1001::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1100::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1200::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1300::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1400::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1500::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1600::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1700::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1800::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1900::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1a00::/48 | Valid | RIR databaseAPNIC | 634 100% |
| 2404:bc80:1b00::/48 | Valid | RIR databaseAPNIC | 634 100% |
AS-SET
AS64072's PeeringDB record names no AS-SET.
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 64 are in fix.csv.
- Route object: not announced64
Route objects not announced
Route objects with origin AS64072 whose prefix no peer sees AS64072 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.25.120.0/22 | APNIC | Valid |
| 103.25.120.0/23 | APNIC | Valid |
| 103.25.122.0/23 | APNIC | Valid |
| 2404:bc80::/32 | APNIC | Valid |
| 2404:bc80:9000::/47 | APNIC | Valid |
| 2404:bc80:9000::/48 | APNIC | Valid |
| 2404:bc80:9001::/48 | APNIC | Valid |
| 2404:bc80:9002::/47 | APNIC | Valid |
| 2404:bc80:9002::/48 | APNIC | Valid |
| 2404:bc80:9003::/48 | APNIC | Valid |
| 2404:bc80:9004::/47 | APNIC | Valid |
| 2404:bc80:9004::/48 | APNIC | Valid |
| 2404:bc80:9005::/48 | APNIC | Valid |
| 2404:bc80:9006::/47 | APNIC | Valid |
| 2404:bc80:9006::/48 | APNIC | Valid |
| 2404:bc80:9007::/48 | APNIC | Valid |
| 2404:bc80:9008::/47 | APNIC | Valid |
| 2404:bc80:9008::/48 | APNIC | Valid |
| 2404:bc80:9009::/48 | APNIC | Valid |
| 2404:bc80:900a::/47 | APNIC | Valid |
| 2404:bc80:900a::/48 | APNIC | Valid |
| 2404:bc80:900b::/48 | APNIC | Valid |
| 2404:bc80:900c::/47 | APNIC | Valid |
| 2404:bc80:900c::/48 | APNIC | Valid |
| 2404:bc80:900d::/48 | APNIC | Valid |
| 2404:bc80:900e::/47 | APNIC | Valid |
| 2404:bc80:900e::/48 | APNIC | Valid |
| 2404:bc80:900f::/48 | APNIC | Valid |
| 2404:bc80:9010::/47 | APNIC | Valid |
| 2404:bc80:9010::/48 | APNIC | Valid |
| 2404:bc80:9011::/48 | APNIC | Valid |
| 2404:bc80:9012::/47 | APNIC | Valid |
| 2404:bc80:9012::/48 | APNIC | Valid |
| 2404:bc80:9013::/48 | APNIC | Valid |
| 2404:bc80:9014::/47 | APNIC | Valid |
| 2404:bc80:9014::/48 | APNIC | Valid |
| 2404:bc80:9015::/48 | APNIC | Valid |
| 2404:bc80:9016::/47 | APNIC | Valid |
| 2404:bc80:9016::/48 | APNIC | Valid |
| 2404:bc80:9017::/48 | APNIC | Valid |
| 2404:bc80:9018::/47 | APNIC | Valid |
| 2404:bc80:9018::/48 | APNIC | Valid |
| 2404:bc80:9019::/48 | APNIC | Valid |
| 2404:bc80:901a::/47 | APNIC | Valid |
| 2404:bc80:901a::/48 | APNIC | Valid |
| 2404:bc80:901b::/48 | APNIC | Valid |
| 2404:bc80:901c::/47 | APNIC | Valid |
| 2404:bc80:901c::/48 | APNIC | Valid |
| 2404:bc80:901d::/48 | APNIC | Valid |
| 2404:bc80:901e::/47 | APNIC | Valid |
| 2404:bc80:901e::/48 | APNIC | Valid |
| 2404:bc80:901f::/48 | APNIC | Valid |
| 2404:bc80:9020::/47 | APNIC | Valid |
| 2404:bc80:9020::/48 | APNIC | Valid |
| 2404:bc80:9021::/48 | APNIC | Valid |
| 2404:bc80:9022::/47 | APNIC | Valid |
| 2404:bc80:9022::/48 | APNIC | Valid |
| 2404:bc80:9023::/48 | APNIC | Valid |
| 2404:bc80:9024::/47 | APNIC | Valid |
| 2404:bc80:9024::/48 | APNIC | Valid |
| 2404:bc80:9025::/48 | APNIC | Valid |
| 2404:bc80:9026::/47 | APNIC | Valid |
| 2404:bc80:9026::/48 | APNIC | Valid |
| 2404:bc80:9027::/48 | APNIC | Valid |
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.