Network · data from 2026-11-12
AS49666 TIC AS49666
Registry name: TIC-GW-AS Telecommunication Infrastructure Company, IR · PeeringDB
40IPv4 routes
90.0% RPKI valid · 32.5% with a route object
2IPv6 routes
50.0% RPKI valid · 0.0% with a route object
4RPKI invalid
4 origin · 0 maxLength
1No ROA
29 with no route object for this origin
15Low visibility
seen by under 10% of full-table peers
9Route objects not announced
registered with origin AS49666, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS49666, 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.
| 89.251.10.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 104.167.26.0/23 | Invalid: origin | Other origin only | 0 0%low visibility |
| 185.188.16.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 195.146.37.0/24 | Invalid: origin | None | 0 0%low visibility |
| 2001:4188:1b::/48 | No ROA | None | 635 100% |
| 2.188.0.0/16 | Valid | None | 672 100% |
| 2.188.22.0/24 | Valid | Other origin onlycovered by 2.188.0.0/19 | 672 100% |
| 2.189.0.0/16 | Valid | Other origin only | 672 100% |
| 2.189.52.0/23 | Valid | None | 672 100% |
| 2.189.69.0/24 | Valid | None | 672 100% |
| 85.185.0.0/16 | Valid | Other origin only | 672 100% |
| 217.218.67.0/24 | Valid | Other origin onlycovered by 217.218.0.0/16 | 672 100% |
| 217.219.0.0/16 | Valid | Other origin only | 672 100% |
| 2.188.179.0/24 | Valid | None | 670 100% |
| 2.188.184.0/24 | Valid | Other origin only | 670 100% |
| 2.188.187.0/24 | Valid | None | 670 100% |
| 2.189.1.0/24 | Valid | Other origin only | 670 100% |
| 78.38.0.0/16 | Valid | Other origin only | 670 100% |
| 78.39.0.0/16 | Valid | Other origin only | 670 100% |
| 80.191.0.0/16 | Valid | Other origin only | 670 100% |
| 2001:4188:2::/48 | Valid | None | 631 99% |
| 2.189.3.0/24 | Valid | None | 2 0%low visibility |
| 2.188.144.0/24 | Valid | None | 0 0%low visibility |
| 2.189.48.0/23 | Valid | None | 0 0%low visibility |
| 2.189.50.0/23 | Valid | None | 0 0%low visibility |
| 2.189.190.0/23 | Valid | None | 0 0%low visibility |
| 80.191.81.0/24 | Valid | Other origin only | 0 0%low visibility |
| 217.218.104.0/24 | Valid | Other origin onlycovered by 217.218.0.0/16 | 0 0%low visibility |
| 217.218.105.0/24 | Valid | Other origin onlycovered by 217.218.0.0/16 | 0 0%low visibility |
| 2.188.0.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.188.1.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.188.7.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.188.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.188.76.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.188.185.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2.189.44.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.218.0.0/16 | Valid | RIR databaseRIPE | 672 100% |
| 2.188.9.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2.188.23.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2.188.17.0/24 | Valid | RIR databaseRIPE | 0 0%low visibility |
| 2.188.30.0/24 | Valid | RIR databaseRIPE | 0 0%low visibility |
| 195.146.63.0/24 | Valid | RIR databaseRIPE | 0 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS49666: RIPE::AS-TICGW. 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 (AS49666 isn't in the set, or no route object for AS49666 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 | AS49666 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-TICGW | RIPElists itself further down5 member sets in no database: AS-207057, AS-IRNA, AS-MORVA, AS-PCC, AS-SEFROYEK | 930 | 33 | Yes | 25 |
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 48 are in fix.csv.
- ROA: origin4
- ROA: none1
- Route object: none29
- AS-SET: missing member5
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 89.251.10.0/24 | ROAs covering it name AS216397, not AS49666; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS49666 should announce it, add a ROA for AS49666. |
| Route object: none | 89.251.10.0/24 | Route objects for it name AS216397. Add a route object with origin AS49666 in the RIR database for the space. |
| ROA: origin | 104.167.26.0/23 | ROAs covering it name AS216067, not AS49666. If AS49666 should announce it, add a ROA for AS49666. |
| Route object: none | 104.167.26.0/23 | Route objects for it name AS216067. Add a route object with origin AS49666 in the RIR database for the space. |
| ROA: origin | 185.188.16.0/24 | ROAs covering it name AS216067, not AS49666. If AS49666 should announce it, add a ROA for AS49666. |
| Route object: none | 185.188.16.0/24 | Route objects for it name AS216067. Add a route object with origin AS49666 in the RIR database for the space. |
| ROA: origin | 195.146.37.0/24 | ROAs covering it name AS12880, AS60148, not AS49666. If AS49666 should announce it, add a ROA for AS49666. |
| Route object: none | 195.146.37.0/24 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| ROA: none | 2001:4188:1b::/48 | No ROA covers it. Add a ROA for AS49666, maxLength 48. |
| Route object: none | 2001:4188:1b::/48 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.188.0.0/16 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.188.22.0/24 | Route objects for it name AS12880. A route object for 2.188.0.0/19 with origin AS49666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.0.0/16 | Route objects for it name AS12880. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.52.0/23 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.69.0/24 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 85.185.0.0/16 | Route objects for it name AS12880. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 217.218.67.0/24 | Route objects for it name AS12880. A route object for 217.218.0.0/16 with origin AS49666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 217.219.0.0/16 | Route objects for it name AS12880, AS58224. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.188.179.0/24 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.188.184.0/24 | Route objects for it name AS12880. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.188.187.0/24 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.1.0/24 | Route objects for it name AS12880. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 78.38.0.0/16 | Route objects for it name AS12880. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 78.39.0.0/16 | Route objects for it name AS58224. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 80.191.0.0/16 | Route objects for it name AS12880, AS58224. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2001:4188:2::/48 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.3.0/24 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.188.144.0/24 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.48.0/23 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.50.0/23 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 2.189.190.0/23 | No route object for it. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 80.191.81.0/24 | Route objects for it name AS12880. Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 217.218.104.0/24 | Route objects for it name AS12880. A route object for 217.218.0.0/16 with origin AS49666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49666 in the RIR database for the space. |
| Route object: none | 217.218.105.0/24 | Route objects for it name AS12880. A route object for 217.218.0.0/16 with origin AS49666 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49666 in the RIR database for the space. |
| AS-SET: missing member | RIPE::AS-TICGW | AS-TICGW (RIPE) lists AS-207057; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-TICGW | AS-TICGW (RIPE) lists AS-IRNA; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-TICGW | AS-TICGW (RIPE) lists AS-MORVA; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-TICGW | AS-TICGW (RIPE) lists AS-PCC; no IRR database read has it. |
| AS-SET: missing member | RIPE::AS-TICGW | AS-TICGW (RIPE) lists AS-SEFROYEK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS49666 whose prefix no peer sees AS49666 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.177.102.0/24 | RIPE | Invalid: maxLength |
| 2.188.0.0/19 | RIPE | Valid |
| 2.188.2.0/24 | RIPE | Valid |
| 2.188.186.0/24 | RIPE | Valid |
| 2.189.58.0/24 | RIPE | Valid |
| 78.38.245.0/24 | RIPE | Valid |
| 193.162.129.0/24 | RIPE | Invalid: origin |
| 217.218.127.0/24 | RIPE | Valid |
| 2001:4188:0:1::/64 | RIPE | Invalid: origin |
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.