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 not checked
2a04:9307:10::/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 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

13 networks seen before AS216369 in AS paths

Observed upstreams
Families
AS1764 NEXTLAYER-AS 192 433
v6
AS6939 HURRICANE 211 410
v6
AS34927 56 121
v6
AS8218 NEO-ASN 6 30
v6
AS48362 TKSWF-AS 4 12
v4 v6
AS5405 8 11
v4 v6
AS47498 FogIXP 5 7
v6
AS39351 ESAB-AS 4 6
v6
AS41051 4 6
v6
AS8298 3 4
v6
AS205794 RTTW-AS 2 3
v6
AS209022 2 3
v6
AS50869 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS216369 in AS paths

Observed downstreams
Families
AS216105 259 361
v6
AS200273 6 8
v4

No rows match “”.

Showing – of

Uncertain adjacencies

16 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS47692 2 6
v6
AS49544 i3Dnet 2 6
v6
AS51184 2 6
v6
AS59890 2 6
v6
AS35369 3 4
v4 v6
AS3212 2 3
v6
AS6720 2 3
v6
AS31510 2 3
v6
AS34288 2 3
v6
AS40994 2 3
v6
AS41666 2 3
v6
AS47147 2 3
v6
AS58299 OPENFACTORY-AS 2 3
v6
AS209823 2 3
v6
AS215628 2 3
v6
AS212635 1 1
v6

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.