Skip to main content

AS216369

jkdev

=========================================

Registry

Authoritative registration data

AS number
216369
Name
jkdev
Organisation
=========================================
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

2

Total announced

2

Announced prefixes

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

Prefixes announced by AS216369
2a05:dfc1:d100::/40 IPv6 /40 RPKI valid
2a04:9307:10::/44 IPv6 /44 RPKI valid

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 AS216369
Address families
FogIXP 1,000 Mbps IPv6
VIX 500 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 AS216369 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS216369 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 135 257
v6
AS1764 NEXTLAYER-AS 92 162
v6
AS34927 iFog-GmbH 18 43
v6
AS48362 TKSWF-AS 4 9
v4 v6
AS39351 ESAB-AS 2 3
v6
AS205794 RTTW-AS 2 3
v6
AS6663 TTI-NET 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS216369 in AS paths

Observed downstreams
Families
AS216105 F-WuTS 139 174
v6
AS200273 kNET 12 24
v4 v6

No rows match “”.

Showing – of

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.