Skip to main content

AS29186

Rivne-Telecom-AS

LLC Rivne-Telecom

Registry

Authoritative registration data

AS number
29186
Name
Rivne-Telecom-AS
Organisation
LLC Rivne-Telecom
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 AS29186
193.104.16.0/24 IPv4 /24 not checked
195.230.96.0/24 IPv4 /24 not checked
195.85.219.0/24 IPv4 /24 not checked
91.220.174.0/24 IPv4 /24 not checked
2001:678:abc::/48 IPv6 /48 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 AS29186
Address families
DTEL-IX: PUBLIC 10,000 Mbps IPv4
RV-IX 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 AS29186 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS29186 in AS paths

Observed upstreams
Families
AS35297 DATALINE-AS 323 1,679
v4 v6
AS6849 UKRTELNET 40 160
v4
AS3326 Datagroup 40 110
v4 v6
AS48648 KYIVLINK 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS29186 in AS paths

Observed downstreams
Families
AS57954 ASBUDKO 8 39
v4
AS50392 CAMPUS-RV-as 1 1
v6

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 8
v4
AS48919 UA-CITY-AS 1 4
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.