Network · data from 2026-11-12
AS33951 "FORWEB" S.C. Monika Bodetko, Tomasz Pawlowski
Registry name: FORWEB "FORWEB" S.C. Monika Bodetko, Tomasz Pawlowski, PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS33951, 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.
| 95.175.1.0/24 | Valid | Nonecovered by 95.175.0.0/19 | 673 100% |
| 95.175.10.0/24 | Valid | Nonecovered by 95.175.0.0/19 | 673 100% |
| 95.175.13.0/24 | Valid | Nonecovered by 95.175.0.0/19 | 30 4%low visibility |
| 91.193.96.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 95.175.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.239.206.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.63.132.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.11.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.175.0.0/19 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS33951: AS-FORWEB. 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 (AS33951 isn't in the set, or no route object for AS33951 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 | AS33951 in it | Not covered |
|---|---|---|---|---|---|
| AS-FORWEB | RIPE | 9 | 1 | 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 6 are in fix.csv.
- Route object: none3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 95.175.1.0/24 | No route object for it. A route object for 95.175.0.0/19 with origin AS33951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33951 in the RIR database for the space. |
| Route object: none | 95.175.10.0/24 | No route object for it. A route object for 95.175.0.0/19 with origin AS33951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33951 in the RIR database for the space. |
| Route object: none | 95.175.13.0/24 | No route object for it. A route object for 95.175.0.0/19 with origin AS33951 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33951 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS33951 whose prefix no peer sees AS33951 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.214.0.0/22 | RIPE | Invalid: origin |
| 2a04:1200::/29 | RIPE | Valid |
| 2a10:f781:10:8ffe::/64 | RIPE | No ROA |
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.