Skip to main content

AS49158

WIFINITY

WIFINITY NETWORKS LIMITED

Registry

Authoritative registration data

AS number
49158
Name
WIFINITY
Organisation
WIFINITY NETWORKS LIMITED
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

1

Total announced

8

Announced prefixes

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

Prefixes announced by AS49158
37.60.64.0/18 IPv4 /18 not checked
212.9.96.0/19 IPv4 /19 not checked
37.60.64.0/19 IPv4 /19 not checked
37.60.96.0/19 IPv4 /19 not checked
212.9.112.0/20 IPv4 /20 not checked
212.9.96.0/20 IPv4 /20 not checked
212.9.124.0/22 IPv4 /22 not checked
2a03:4307::/32 IPv6 /32 RPKI valid

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 AS49158
Address families
LINX LON1: Main 400,000 Mbps IPv4 · IPv6
LONAP: LON0 400,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 AS49158 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

43 networks seen before AS49158 in AS paths

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS49158 in AS paths

Observed downstreams
Families
AS51048 NEXT-CONNEX 4,118 11,248
v4 v6
AS197545 Era4-ASN 362 668
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

35 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.