Network · data from 2026-11-12
AS48492 IQ-Online I.Q Online for Internet Services and Communications LLC
Registry name: IQ-Online I.Q Online for Internet Services and Communications LLC, IQ · not in PeeringDB
55IPv4 routes
100.0% RPKI valid · 60.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
22 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
10Route objects not announced
registered with origin AS48492, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS48492, 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.
| 85.155.196.0/24 | Valid | None | 673 100% |
| 85.155.197.0/24 | Valid | None | 673 100% |
| 85.155.198.0/24 | Valid | None | 673 100% |
| 85.155.199.0/24 | Valid | None | 673 100% |
| 85.155.200.0/24 | Valid | None | 673 100% |
| 85.155.201.0/24 | Valid | None | 673 100% |
| 85.155.202.0/24 | Valid | None | 673 100% |
| 85.155.203.0/24 | Valid | None | 673 100% |
| 85.155.204.0/24 | Valid | None | 673 100% |
| 85.155.205.0/24 | Valid | None | 673 100% |
| 85.155.206.0/24 | Valid | None | 673 100% |
| 85.155.207.0/24 | Valid | None | 673 100% |
| 95.142.145.0/24 | Valid | None | 673 100% |
| 95.142.146.0/24 | Valid | None | 673 100% |
| 95.142.147.0/24 | Valid | None | 673 100% |
| 185.181.110.0/24 | Valid | Other origin onlycovered by 185.181.108.0/22 | 673 100% |
| 185.181.111.0/24 | Valid | Other origin onlycovered by 185.181.108.0/22 | 673 100% |
| 85.155.192.0/24 | Valid | None | 672 100% |
| 85.155.193.0/24 | Valid | None | 672 100% |
| 85.155.194.0/24 | Valid | None | 672 100% |
| 85.155.195.0/24 | Valid | None | 672 100% |
| 95.142.144.0/24 | Valid | Other origin only | 672 100% |
| 62.201.239.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.222.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.222.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.222.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.222.63.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.56.192.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.56.192.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.56.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.56.194.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.56.195.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.224.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.224.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.224.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.225.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.226.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.75.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.181.108.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.181.108.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.181.109.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.204.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.205.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.8.242.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.8.243.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.8.244.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.8.245.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.8.246.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.8.247.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.8.240.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 5.8.241.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.187.204.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS48492 isn't in PeeringDB, where networks name their AS-SET.
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 32 are in fix.csv.
- Route object: none22
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 85.155.196.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.197.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.198.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.199.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.200.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.201.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.202.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.203.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.204.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.205.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.206.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.207.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 95.142.145.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 95.142.146.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 95.142.147.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 185.181.110.0/24 | Route objects for it name AS44217. A route object for 185.181.108.0/22 with origin AS48492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 185.181.111.0/24 | Route objects for it name AS44217. A route object for 185.181.108.0/22 with origin AS48492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.192.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.193.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.194.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 85.155.195.0/24 | No route object for it. Add a route object with origin AS48492 in the RIR database for the space. |
| Route object: none | 95.142.144.0/24 | Route objects for it name AS25180. Add a route object with origin AS48492 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48492 whose prefix no peer sees AS48492 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.8.240.0/21 | RIPE | Valid |
| 2a0d:4f00::/29 | RIPE | Valid |
| 2a0d:4f00::/32 | RIPE | Valid |
| 2a0d:4f01::/32 | RIPE | Valid |
| 2a0d:4f02::/32 | RIPE | Valid |
| 2a0d:4f03::/32 | RIPE | Valid |
| 2a0d:4f04::/32 | RIPE | Valid |
| 2a0d:4f05::/32 | RIPE | Valid |
| 2a0d:4f06::/32 | RIPE | Valid |
| 2a0d:4f07::/32 | 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.