Skip to main content

AS39679

ASJZTKFT

JZT Informatikai Kft.

Registry

Authoritative registration data

AS number
39679
Name
ASJZTKFT
Organisation
JZT Informatikai Kft.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS39679
193.188.192.0/24 IPv4 /24 not checked
213.181.201.0/24 IPv4 /24 not checked
45.67.156.0/24 IPv4 /24 not checked
45.67.158.0/24 IPv4 /24 not checked
45.67.159.0/24 IPv4 /24 not checked
77.221.49.0/24 IPv4 /24 not checked
79.172.220.0/24 IPv4 /24 not checked
2a09:7ac0::/32 IPv6 /32 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 AS39679
Address families
BIX 10,000 Mbps IPv4

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 AS39679 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS39679 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 687 2,928
v4 v6
AS215366 BGN 30 189
v4 v6
AS6939 HURRICANE 64 79
v6
AS33891 CORE-BACKBONE 8 63
v4
AS47692 NESSUS 2 32
v4 v6
AS15576 NTS 3 21
v4
AS6663 TTI-NET 1 7
v4
AS15958 CETIN_doo_AS 1 7
v4
AS21215 UGNI 1 7
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS39679 in AS paths

Observed downstreams
Families
AS215366 BGN 305 636
v4 v6
AS197889 MICROSYSTEM 38 47
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 16
v4 v6
AS40994 Alwyzon 1 8
v4 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.