AS47480 Blue Tiger Solutions
AS47480 is operated by Blue Tiger Solutions and registered with RIPE NCC (GB) since 2008-06-25.
It announces 9 IPv4 and 0 IPv6 prefixes, 0% of them RPKI valid.
RIPE RIS sees 52 upstream and peer networks and 0 downstream networks next to it.
PeeringDB lists it as a Content network at 3 internet exchanges and 2 facilities. Its peering policy is open.
| Name | Blue Tiger Solutions |
|---|---|
| Registry (RIR) | RIPE NCC |
| Country | United Kingdom (GB) |
| Delegated on | 2008-06-25 |
| Network type | Content, Europe |
| Peering policy | Open |
| IRR as-set | AS-BTS |
| Prefixes (IPv4 / IPv6) | 9 / 0 |
| RPKI valid | 0% (0 / 9) |
| Upstreams and peers | 52 |
| Downstream networks | 0 |
| Website | bluetigersolutions.com |
Routing health
- AS47480 announces 9 IPv4 and 0 IPv6 prefixes.
- No IPv6 prefixes announced.
- 9 announced prefixes are not covered by a ROA of AS47480 (they may have none, or another network’s).
- 52 upstreams and peers, 0 downstream networks seen.
For every check with the fix (IRR route objects, the RPKI state of each route, reverse DNS and the registration), run the full network report.
Announced prefixes 9
- 46.254.112.0/21
- 46.254.112.0/22
- 46.254.116.0/22
- 95.128.216.0/21
- 95.128.216.0/22
- 95.128.220.0/22
- 95.128.220.0/24
- 185.48.160.0/22
- 185.48.161.0/24
Upstreams and peers 52
The networks RIPE RIS sees next to AS47480 in BGP paths, the most visible first.
Peering
Peering policy: Open. Suggested max-prefix limits: 20 IPv4, 1 IPv6. PeeringDB record
| Exchange | Ports | Speed | Route server |
|---|---|---|---|
| LINX LON1: Main | 1 | 10G | Yes |
| LINX LON2 | 1 | 10G | Yes |
| LONAP: LON0 | 1 | 10G | Yes |
| Facility | City | Country |
|---|---|---|
| Redcentric London Data Centre | London | GB |
| Telehouse - London (Docklands North) | London | GB |
More about AS47480
Sources: RIR delegation data and PeeringDB (updated daily); routing from RIPEstat (RIPE NCC RIS and RPKI), refreshed daily. Routing data from 2026-11-14 01:46 UTC. The country is where the AS number was registered, not necessarily where the network operates.