Skip to main content

AS200964

ISISCOM

Isis-Com Kft.

Registry

Authoritative registration data

AS number
200964
Name
ISISCOM
Organisation
Isis-Com Kft.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

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

Prefixes announced by AS200964
193.226.197.0/24 IPv4 /24 not checked
193.226.235.0/24 IPv4 /24 not checked
195.184.5.0/24 IPv4 /24 not checked
195.184.8.0/24 IPv4 /24 not checked
77.221.36.0/24 IPv4 /24 not checked
77.221.37.0/24 IPv4 /24 not checked
77.221.38.0/24 IPv4 /24 not checked
77.221.39.0/24 IPv4 /24 not checked
77.221.40.0/24 IPv4 /24 not checked
77.221.41.0/24 IPv4 /24 not checked
77.221.42.0/24 IPv4 /24 not checked
2a10:4941: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 AS200964
Address families
BIX 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 AS200964 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS200964 in AS paths

Observed upstreams
Families
AS12301 Invitech 238 2,513
v4 v6
AS41206 United-Telecom-HU-AS 88 1,104
v4 v6
AS6939 HURRICANE 77 341
v4 v6
AS47692 NESSUS 2 48
v4 v6
AS6663 TTI-NET 1 12
v4 v6
AS15576 NTS 1 11
v4
AS15958 CETIN_doo_AS 1 11
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS200964 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

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