Skip to main content

AS47254

WFC-AS

--- Transit L3 TIM ---

Registry

Authoritative registration data

AS number
47254
Name
WFC-AS
Organisation
--- Transit L3 TIM ---
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS47254
185.9.148.0/22 IPv4 /22 RPKI valid
185.9.148.0/24 IPv4 /24 not checked
185.9.149.0/24 IPv4 /24 RPKI valid
185.9.150.0/24 IPv4 /24 not checked
185.9.151.0/24 IPv4 /24 not checked
212.102.98.0/24 IPv4 /24 not checked
46.30.219.0/24 IPv4 /24 RPKI valid
46.30.221.0/24 IPv4 /24 not checked
2a02:d1c0::/29 IPv6 /29 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 AS47254
Address families
MINAP Milan: MINAP 10,000 Mbps IPv4 · IPv6

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

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS47254 in AS paths

Observed upstreams
Families
AS3269 ASN-IBSNAZ 223 2,196
v4 v6
AS6939 HURRICANE 119 474
v4 v6
AS14840 ASN14840 2 45
v4 v6
AS22356 ASN22356 5 41
v4 v6
AS60501 SIRIUSTEC-IT 13 30
v6
AS24961 MYLOC-AS 2 18
v4 v6
AS9009 M247 1 8
v4
AS9498 BBIL-AP 1 8
v4
AS263444 ASN263444 1 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS47254 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

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.