Skip to main content

AS48464

FUTUROEXITO-AS

Futuro Exito Sp. z o.o.

Registry

Authoritative registration data

AS number
48464
Name
FUTUROEXITO-AS
Organisation
Futuro Exito Sp. z o.o.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS48464
109.200.80.0/20 IPv4 /20 RPKI not found
94.230.16.0/20 IPv4 /20 not checked
185.251.196.0/24 IPv4 /24 RPKI not found
185.251.197.0/24 IPv4 /24 not checked
185.251.198.0/24 IPv4 /24 not checked
2a0a:16c0::/32 IPv6 /32 RPKI not found

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 AS48464
Address families
EPIX.Warszawa 10,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 AS48464 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS48464 in AS paths

Observed upstreams
Families
AS12912 TMPL 850 2,136
v4 v6
AS62081 EPIX-WAW-GlobalMix 843 1,554
v4

No rows match “”.

Showing – of

Observed downstreams

10 networks seen after AS48464 in AS paths

Observed downstreams
Families
AS60399 ADAMPOLNET 153 782
v4
AS5582 SSPW-WL-AS 131 374
v4 v6
AS48992 ALKM-AS 263 355
v4 v6
AS41036 LUB-ZETO-AS 168 197
v4
AS43968 TOP-NET-AS 168 197
v4
AS52124 FALCOM-AS 168 197
v4
AS50777 SADAPELUB-AS 167 194
v4
AS199936 105 125
v4
AS42573 Skrivanek 65 82
v4
AS42520 PL-Lublin-UM-AS 53 60
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 7 11
v4
AS49544 i3Dnet 7 11
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.