Network · data from 2026-11-12
AS47544 IQ PL
Registry name: IQPL-AS IQ PL Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47544, 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.
| 46.248.167.212/32 | Invalid: maxLength | Nonecovered by 46.248.160.0/19 | 2 0%low visibility |
| 80.209.248.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 85.113.64.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 91.199.51.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 176.126.248.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 185.31.80.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 195.192.240.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 46.248.160.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 86.111.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 185.110.48.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.110.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.110.51.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.106.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:7400::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS47544: RIPE::AS-IQPL. 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 (AS47544 isn't in the set, or no route object for AS47544 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 | AS47544 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-IQPL | RIPE | 10 | 2 | Yes | 1 |
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 15 are in fix.csv.
- ROA: maxLength1
- ROA: none6
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 46.248.167.212/32 | ROA 46.248.160.0/19 AS47544 has maxLength 19; the route is a /32. Raise the maxLength, or add a ROA for 46.248.167.212/32. |
| Route object: none | 46.248.167.212/32 | No route object for it. A route object for 46.248.160.0/19 with origin AS47544 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS47544 in the RIR database for the space. |
| ROA: none | 80.209.248.0/22 | No ROA covers it. Add a ROA for AS47544, maxLength 22. |
| ROA: none | 85.113.64.0/22 | No ROA covers it. Add a ROA for AS47544, maxLength 22. |
| ROA: none | 91.199.51.0/24 | No ROA covers it. Add a ROA for AS47544, maxLength 24. |
| ROA: none | 176.126.248.0/22 | No ROA covers it. Add a ROA for AS47544, maxLength 22. |
| ROA: none | 185.31.80.0/22 | No ROA covers it. Add a ROA for AS47544, maxLength 22. |
| ROA: none | 195.192.240.0/22 | No ROA covers it. Add a ROA for AS47544, maxLength 22. |
Route objects not announced
Route objects with origin AS47544 whose prefix no peer sees AS47544 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 46.248.160.0/24 | RIPE | Invalid: maxLength |
| 46.248.174.0/24 | RIPE | Valid |
| 46.248.183.0/24 | RIPE | Valid |
| 91.244.225.0/24 | RIPE | Invalid: origin |
| 185.110.49.0/24 | RIPE | Valid |
| 2a00:b960::/32 | RIPE | No ROA |
| 2a10:f781:10:371e::/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.