Skip to main content

AS43656

INTERTELECOM-TV

Sumy, Ukraine

Registry

Authoritative registration data

AS number
43656
Name
INTERTELECOM-TV
Organisation
Sumy, Ukraine
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS43656
93.170.64.0/22 IPv4 /22 not checked
93.170.68.0/22 IPv4 /22 not checked
194.28.4.0/23 IPv4 /23 not checked
194.28.6.0/23 IPv4 /23 not checked
91.198.83.0/24 IPv4 /24 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 AS43656
Address families
DTEL-IX: PUBLIC 10,000 Mbps IPv4
Giganet IXN: Global exchange 40,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 AS43656 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS43656 in AS paths

Observed upstreams
Families
AS35297 195 1,230
v4
AS3326 94 622
v4
AS3303 SWISSCOM 3 15
v4
AS6663 1 5
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS43656 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 35
v4
AS49544 i3Dnet 1 10
v4
AS48919 1 5
v4
AS209823 1 5
v4

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.