Skip to main content

AS34968

iunxi

|

Registry

Authoritative registration data

AS number
34968
Name
iunxi
Organisation
|
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

2

Total announced

16

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS34968
46.38.192.0/19 IPv4 /19 RPKI valid
89.207.24.0/21 IPv4 /21 RPKI valid
95.155.184.0/21 IPv4 /21 not checked
193.201.48.0/22 IPv4 /22 RPKI not found
193.238.240.0/22 IPv4 /22 not checked
45.152.236.0/22 IPv4 /22 RPKI not found
89.207.24.0/22 IPv4 /22 RPKI valid
89.207.28.0/22 IPv4 /22 not checked
193.169.26.0/23 IPv4 /23 RPKI not found
193.169.92.0/23 IPv4 /23 RPKI valid
193.53.104.0/23 IPv4 /23 RPKI not found
193.53.96.0/23 IPv4 /23 RPKI not found
95.155.188.0/24 IPv4 /24 RPKI valid
95.155.191.0/24 IPv4 /24 RPKI valid
2a01:710::/32 IPv6 /32 RPKI valid
2a01:710:17::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS34968
Address families
AMS-IX 10,000 Mbps IPv4 · IPv6
NL-ix: Main 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS34968 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

48 networks seen before AS34968 in AS paths

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS34968 in AS paths

Observed downstreams
Families
AS44928 Trixit 249 990
v6
AS30720 VWE-Extranet-AS 423 583
v4 v6
AS47863 SDSK 202 493
v4
AS48645 SOLVINITY-NL-2 258 329
v4
AS203179 ProactMCS 110 158
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

55 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.