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 not checked
94.230.16.0/20 IPv4 /20 not checked
185.251.196.0/24 IPv4 /24 not checked
185.251.197.0/24 IPv4 /24 not checked
185.251.198.0/24 IPv4 /24 not checked
2a0a:16c0::/32 IPv6 /32 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 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

3 networks seen before AS48464 in AS paths

Observed upstreams
Families
AS12912 TMPL 1,415 4,221
v4 v6
AS62081 EPIX-WAW-GlobalMix 1,223 2,588
v4
AS201054 EPIX-PolMix 10 18
v4

No rows match “”.

Showing of

Observed downstreams

10 networks seen after AS48464 in AS paths

Observed downstreams
Families
AS60399 264 1,545
v4
AS48992 469 727
v4 v6
AS5582 SSPW-WL-AS 217 708
v4 v6
AS41036 288 384
v4
AS50777 288 384
v4
AS43968 287 383
v4
AS199936 183 238
v4
AS42520 PL-Lublin-UM-AS 90 124
v4
AS42573 95 123
v4
AS52124 FALCOM-AS 13 13
v4

No rows match “”.

Showing of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

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