Network · data from 2026-11-12
AS203641 B3 Online
Registry name: B3-ONLINE Safety Capital, S.L, ES · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203641, 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.
| 193.111.170.0/24 | No ROA | Other origin only | 3 0%low visibility |
| 176.56.89.0/24 | Valid | Nonecovered by 176.56.88.0/23 | 673 100% |
| 185.107.160.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 5.182.160.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.107.160.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.107.161.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a0b:dc40::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS203641: AS203641. 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 (AS203641 isn't in the set, or no route object for AS203641 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 | AS203641 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS203641 | A single AS number, not a set: AS203641 (this network), 20 route objects. | |||||
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 18 are in fix.csv.
- ROA: none1
- Route object: none2
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.111.170.0/24 | No ROA covers it. Add a ROA for AS203641, maxLength 24. |
| Route object: none | 193.111.170.0/24 | Route objects for it name AS834. Add a route object with origin AS203641 in the RIR database for the space. |
| Route object: none | 176.56.89.0/24 | No route object for it. A route object for 176.56.88.0/23 with origin AS203641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203641 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS203641 whose prefix no peer sees AS203641 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.182.160.0/24 | RIPE | Valid |
| 5.182.161.0/24 | RIPE | Valid |
| 5.182.162.0/24 | RIPE | Valid |
| 5.182.163.0/24 | RIPE | Valid |
| 176.56.88.0/23 | RIPE | Valid |
| 185.84.207.0/24 | RIPE | Valid |
| 185.107.162.0/24 | RIPE | Valid |
| 185.107.163.0/24 | RIPE | Valid |
| 185.218.252.0/22 | RIPE | Valid |
| 185.218.252.0/24 | RIPE | Valid |
| 185.218.253.0/24 | RIPE | Valid |
| 185.218.254.0/24 | RIPE | Valid |
| 185.218.255.0/24 | RIPE | Valid |
| 193.111.196.0/23 | RIPE | No ROA |
| 2a0b:dc40:a1fe::/48 | RIPE | Invalid: maxLength |
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.