bgpreport

Network · data from 2026-11-12

AS41625 ETSERVICE-AS Express Teleservice Corp

Registry name: ETSERVICE-AS Express Teleservice Corp, US · not in PeeringDB

7IPv4 routes 57.1% RPKI valid · 100.0% with a route object
6IPv6 routes 33.3% 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
7Route objects not announced registered with origin AS41625, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS41625, 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.
82.129.44.0/24 No ROA Other IRR onlyRADB 671 100% 67
2001:df0:69::/48 No ROA Other IRR onlyRIPE-NONAUTH 635 100% 67
154.48.203.0/24 No ROA Other IRR onlyRADB 155 23% 50
203.189.26.0/23 No ROA RIR databaseAPNIC, NTTCOM, RADB, RIPE-NONAUTH 673 100% 67
2a0d:e500::/32 No ROA RIR databaseRIPE 636 100% 67
2620:11:a000::/48 No ROA RIR databaseARIN 635 100% 67
2a0d:e500:2::/48 No ROA RIR databaseRIPE 605 95% 67
89.31.240.0/21 Valid RIR databaseRIPE 673 100% 67
185.219.90.0/24 Valid RIR databaseRIPE 673 100% 67
192.210.11.0/24 Valid RIR databaseARIN 673 100% 67
2a00:8900::/32 Valid RIR databaseRIPE 635 100% 67
2a00:8900:ffff::/48 Valid RIR databaseRIPE 635 100% 67
204.225.223.0/24 Valid RIR databaseARIN, NTTCOM, RADB 436 65% 65

AS-SET

AS41625 isn't in PeeringDB, where networks name their 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 17 are in fix.csv.

  • ROA: none7
  • Route object: RIR3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none82.129.44.0/24No ROA covers it. Add a ROA for AS41625, maxLength 24.671 of 673
Route object: RIR82.129.44.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2001:df0:69::/48No ROA covers it. Add a ROA for AS41625, maxLength 48.635 of 636
Route object: RIR2001:df0:69::/48Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.635 of 636
ROA: none154.48.203.0/24No ROA covers it. Add a ROA for AS41625, maxLength 24.155 of 673
Route object: RIR154.48.203.0/24Route object only in RADB. Add it in the RIR database for the space.155 of 673
ROA: none203.189.26.0/23No ROA covers it. Add a ROA for AS41625, maxLength 23.673 of 673
ROA: none2a0d:e500::/32No ROA covers it. Add a ROA for AS41625, maxLength 32.636 of 636
ROA: none2620:11:a000::/48No ROA covers it. Add a ROA for AS41625, maxLength 48.635 of 636
ROA: none2a0d:e500:2::/48No ROA covers it. Add a ROA for AS41625, maxLength 48.605 of 636

Route objects not announced

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

89.31.240.0/23RIPEInvalid: maxLength
89.31.242.0/24RIPEValid
89.31.246.0/24RIPEValid
203.189.26.0/24NTTCOM, RADBNo ROA
203.189.27.0/24NTTCOM, RADBNo ROA
2a0d:e500:1::/48RIPENo ROA
2a0d:e500:3::/48RIPENo 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.