Skip to main content

AS39817

OVANET

ORG-Oa141-RIPE

Registry

Authoritative registration data

AS number
39817
Name
OVANET
Organisation
ORG-Oa141-RIPE
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS39817
81.91.208.0/20 IPv4 /20 not checked
83.119.14.0/24 IPv4 /24 not checked
2a02:2310::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS39817 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS39817 in AS paths

Observed upstreams
Families
AS16019 VODAFONE-CZ-AS 228 642
v4 v6
AS6939 HURRICANE 106 187
v4 v6
AS8218 NEO-ASN 6 42
v4 v6
AS22356 ASN22356 7 15
v4 v6
AS1764 NEXTLAYER-AS 3 15
v4 v6
AS14840 ASN14840 2 15
v4 v6
AS4455 BSO 2 7
v4 v6
AS6204 ZET-NET 1 2
v4
AS6663 TTI-NET 1 2
v4
AS21215 UGNI 1 2
v4
AS44306 Omonia 1 2
v4
AS263444 ASN263444 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS39817 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 33
v4 v6
AS49544 i3Dnet 1 6
v4 v6
AS51184 FONIRA 1 6
v4 v6
AS212483 level86 1 6
v4 v6
AS6881 NIXCZ 1 3
v4 v6
AS29504 LBCFREE 1 3
v4 v6
AS36236 NETACTUATE 1 3
v4 v6
AS40994 Alwyzon 1 3
v4 v6
AS198150 SIACOM-AS 1 3
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.