Skip to main content

AS31396

JULE

--------------------------------------

Registry

Authoritative registration data

AS number
31396
Name
JULE
Organisation
--------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS31396
193.30.42.0/24 IPv4 /24 not checked
2a0c:b641:410::/44 IPv6 /44 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 AS31396
Address families
4b42 Internet Exchange Point: Switzerland 1,000 Mbps IPv4 · IPv6
KleyReX: Peering LAN 100 Mbps IPv4 · IPv6
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX NETHERLANDS: Peering LAN 1,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 AS31396 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS31396 in AS paths

Observed upstreams
Families
AS34872 Servperso_Systems 139 173
v4 v6
AS48646 STEFAN6 95 127
v6
AS6939 HURRICANE 14 14
v4
AS25091 IP-Max 3 5
v4 v6
AS14840 ASN14840 2 4
v4
AS34549 MEER-AS 2 3
v4 v6
AS401753 BIXCE 1 2
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS31396 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 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.