Skip to main content

AS35590

OMEGACOM

Omegacom S.R.L.S.

Registry

Authoritative registration data

AS number
35590
Name
OMEGACOM
Organisation
Omegacom S.R.L.S.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS35590
178.239.37.0/24 IPv4 /24 not checked
2a09:3fc0::/29 IPv6 /29 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 AS35590 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS35590 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 140 200
v4 v6
AS47927 WIFIWEB 58 66
v4
AS174 COGENT-174 38 45
v4
AS6939 HURRICANE 8 8
v4
AS49289 Media-Veneto 7 7
v4
AS31543 MYNET-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS35590 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4
AS8218 NEO-ASN 1 2
v4
AS12779 ITGATE 1 1
v4
AS13237 LAMBDANET-AS 1 1
v4
AS24961 MYLOC-AS 1 1
v4
AS49544 i3Dnet 1 1
v4
AS59919 BRAINBOX 1 1
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.