Skip to main content

AS8779

INFOCOM-KM

Khmelnitsky, Ukraine

Registry

Authoritative registration data

AS number
8779
Name
INFOCOM-KM
Organisation
Khmelnitsky, Ukraine
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS8779
78.152.160.0/19 IPv4 /19 not checked
46.252.208.0/20 IPv4 /20 not checked
94.230.192.0/20 IPv4 /20 not checked
185.15.4.0/23 IPv4 /23 not checked
2a00:6740::/32 IPv6 /32 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 AS8779
Address families
DTEL-IX: PUBLIC 10,000 Mbps IPv4 · IPv6
KM-IX old: Main 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 AS8779 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS8779 in AS paths

Observed upstreams
Families
AS28773 AS-MASTER 463 1,831
v4 v6
AS3326 Datagroup 602 1,377
v4 v6
AS3303 SWISSCOM 12 63
v4 v6
AS6663 TTI-NET 2 9
v4 v6
AS48648 KYIVLINK 2 3
v6

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS8779 in AS paths

Observed downstreams
Families
AS29663 546 1,398
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 18
v4 v6
AS48919 UA-CITY-AS 2 9
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.