Autonomous system
AS48185 TEAM_BLUE team.blue backbone
Unclassified RIPE
Summary
team.blue
transit isp belgium
The AS handle TEAM_BLUE is held by team.blue NV.
What it's used for
- The address space carries backbone traffic, as indicated by reverse DNS entries such as
195-90-96-128.bb.team.blueand netnames referencingteam-blue. - The AS announces 512 IPv4 addresses and 1 IPv6 prefix while maintaining 1396 observed neighbours, a ratio that indicates a transit or peering-heavy role rather than a residential access network.
- Traffic from this AS consists of routed internet traffic for team.blue's customer base and peering partners, consistent with its operation as a Belgian internet service provider and carrier.
Notable
- Registrants for the announced prefix
195.90.96.0/23include Team Blue Carrier Limited, team.blue Operators, and team.blue Abuse, which align with the announcer identity. - The address inventory is compact, consisting of a single IPv4 /23 block and one IPv6 /32, suggesting a focused operational footprint.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
Recorded at 5 exchanges in 3 countries, largest first.
| Exchange | Location | Their address |
|---|---|---|
| LINX LON1 | London, United Kingdom | 195.66.224.223 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.214.144 |
| Neutral Internet Exchange | Amsterdam, Netherlands | 193.239.119.253 |
| London Network Access Point | London, United Kingdom | 5.57.80.24 |
| Belgian National Internet Exchange | Brussels, Belgium | 194.53.172.44 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-27, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 512 addresses IPv6 1 prefixes
| Country | Name | Prefixes |
|---|---|---|
| BE | Belgium | 2 |
Registry
Allocation record
- Registry
- RIPE
- Handle
AS48185- Registry name
- team_blue
- Registrant
- team.blue NV
- Abuse contact
- abuse@team.blue
- Registered
- 2008-10-22
- Last changed
- 2025-10-10
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Team Blue
- Also known as
- team.blue
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Selective
- IRR as-set
AS48185:AS-TEAMBLUE- Present at
- 6 exchanges
- Facilities
- 7 facilities
- Website
- https://team.blue
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 50% valid · 1 valid, 1 with no ROA
- ROAs
- 2 authorising AS48185
- ASPA
- no ASPA record
- IRR
- 100% registered · 2 of 2 announcements
- Route objects
- 5 naming AS48185
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 446 networks and 1,852 prefixes, as published 2026-10-27. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere