Skip to main content

AS47480

BlueTigerSolutions-AS

Blue Tiger Solutions Limited

Registry

Authoritative registration data

AS number
47480
Name
BlueTigerSolutions-AS
Organisation
Blue Tiger Solutions Limited
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

0

Total announced

10

Announced prefixes

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

Prefixes announced by AS47480
46.254.112.0/21 IPv4 /21 not checked
95.128.216.0/21 IPv4 /21 not checked
185.48.160.0/22 IPv4 /22 not checked
46.254.112.0/22 IPv4 /22 not checked
46.254.116.0/22 IPv4 /22 not checked
95.128.216.0/22 IPv4 /22 not checked
95.128.220.0/22 IPv4 /22 not checked
185.48.161.0/24 IPv4 /24 not checked
194.62.28.0/24 IPv4 /24 not checked
95.128.220.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 AS47480
Address families
LINX LON1: Main 10,000 Mbps IPv4
LINX LON2 10,000 Mbps IPv4
LONAP: LON0 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 AS47480 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

52 networks seen before AS47480 in AS paths

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS47480 in AS paths

Observed downstreams
Families
AS16351 1 1
v4
AS59621 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

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