Network · data from 2026-11-12
AS48185 Team Blue
Registry name: team_blue team.blue NV, BE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48185, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 195.90.96.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 2a02:2b8::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS48185: AS48185:AS-TEAMBLUE. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS48185 isn't in the set, or no route object for AS48185 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS48185 in it | Not covered |
|---|---|---|---|---|---|
| AS48185:AS-TEAMBLUE | RIPE | 37 | 18 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.90.96.0/23 | No ROA covers it. Add a ROA for AS48185, maxLength 23. |
Route objects not announced
Route objects with origin AS48185 whose prefix no peer sees AS48185 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 62.193.224.0/19 | RIPE | No ROA |
| 85.8.228.0/24 | RIPE | Valid |
| 2a02:2b8:2000::/35 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.