Skip to main content

AS44193

UBNIX-X

Ukrainian Backbone Networks LLC

Registry

Authoritative registration data

AS number
44193
Name
UBNIX-X
Organisation
Ukrainian Backbone Networks LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS44193
194.110.204.0/24 IPv4 /24 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 AS44193
Address families
Giganet IXN Amsterdam 100,000 Mbps IPv4 · IPv6
Giganet IXN Frankfurt 100,000 Mbps IPv4 · IPv6
Giganet IXN Kharkіv: Kharkov local exchange 100,000 Mbps IPv4 · IPv6
Giganet IXN Lviv 100,000 Mbps IPv4 · IPv6
Giganet IXN Odesa: Odessa local exchange 100,000 Mbps IPv4 · IPv6
Giganet IXN Warsaw: Warsaw local exchange 100,000 Mbps IPv4 · IPv6
Giganet IXN Zaporizhia 100,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 AS44193 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS44193 in AS paths

Observed upstreams
Families
AS28907 MIROHOST 388 599
v4 v6
AS6939 HURRICANE 30 45
v4
AS14840 ASN14840 4 12
v4
AS22356 ASN22356 3 4
v4 v6
AS6663 TTI-NET 2 4
v4 v6
AS13194 BITE 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS44193 in AS paths

Observed downstreams
Families
AS61159 GIGANET-CDN 291 519
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 15
v4
AS48919 UA-CITY-AS 2 4
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.