bgpreport

Network · data from 2026-11-12

AS138401 TupleTech Corporation, TupleTech Corporation

Registry name: TUPLENET2-AS-AP - TupleTech Corporation, CN · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
9IPv6 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
1Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS138401, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS138401, 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.
143.246.55.0/24 Valid RIR databaseRIPE 671 100% 67
2406:840:f868::/48 Valid RIR databaseAPNIC 635 100% 69
2406:840:f869::/48 Valid RIR databaseAPNIC 635 100% 67
2406:840:f86c::/48 Valid RIR databaseAPNIC 635 100% 69
2406:840:f860::/48 Valid RIR databaseAPNIC, RADB 634 100% 70
2406:840:f861::/48 Valid RIR databaseAPNIC 634 100% 68
2406:840:f862::/48 Valid RIR databaseAPNIC 634 100% 68
2406:840:f863::/48 Valid RIR databaseAPNIC 634 100% 68
2406:840:fea1::/48 Valid RIR databaseAPNIC 634 100% 69
2406:840:f864::/48 Valid RIR databaseAPNIC 1 0%low visibility 3

AS-SET

AS138401'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 27 are in fix.csv.

  • Route object: not announced27

Route objects not announced

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

103.124.158.0/23NTTCOM, RADBNo ROA
103.124.158.0/24NTTCOM, RADBNo ROA
103.124.159.0/24NTTCOM, RADBNo ROA
2406:840:f860::/44APNICValid
2406:840:f860::/45APNICValid
2406:840:f860::/46APNICValid
2406:840:f860::/47APNICValid
2406:840:f862::/47APNICValid
2406:840:f864::/46APNICValid
2406:840:f864::/47APNICValid
2406:840:f865::/48APNICValid
2406:840:f866::/47APNICValid
2406:840:f866::/48APNICValid
2406:840:f867::/48APNICValid
2406:840:f868::/45APNICValid
2406:840:f868::/46APNICValid
2406:840:f868::/47APNICValid
2406:840:f86a::/47APNICValid
2406:840:f86a::/48APNICValid
2406:840:f86b::/48APNICValid
2406:840:f86c::/46APNICValid
2406:840:f86c::/47APNICValid
2406:840:f86d::/48APNICValid
2406:840:f86e::/47APNICValid
2406:840:f86e::/48APNICValid
2406:840:f86f::/48APNICValid
2a13:9500:1c5::/48RIPEValid

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.