Skip to main content

AS24577

ONEFONE

Onefone SA

Registry

Authoritative registration data

AS number
24577
Name
ONEFONE
Organisation
Onefone SA
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS24577
91.187.224.0/19 IPv4 /19 not checked
176.120.120.0/21 IPv4 /21 not checked
185.108.68.0/22 IPv4 /22 not checked
82.177.142.0/24 IPv4 /24 not checked
82.177.189.0/24 IPv4 /24 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 AS24577
Address families
EPIX.Warszawa 10,000 Mbps IPv4 · IPv6
TPIX PL 100,000 Mbps IPv4

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS24577 in AS paths

Observed upstreams
Families
AS62081 599 2,076
v4
AS20804 ASN-TELENERGO 270 1,084
v4
AS5617 36 140
v4
AS6204 3 11
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS24577 in AS paths

Observed downstreams
Families
AS203828 330 1,018
v4
AS199894 293 388
v4

No rows match “”.

Showing of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 12
v4
AS24482 SGGS-AS-AP 2 6
v4
AS28917 2 6
v4
AS36236 NETACTUATE 2 6
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.