Network · data from 2026-11-12
AS213241 TechIT.be
Registry name: TECHIT TECHIT.BE SRL, BE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213241, 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.
| 80.81.192.0/21 | Invalid: origin | None | 2 0%low visibility |
| 80.249.208.0/21 | Invalid: origin | Other origin only | 2 0%low visibility |
| 195.66.224.0/21 | Invalid: origin | None | 2 0%low visibility |
| 87.238.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.42.52.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.47.38.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.199.110.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.238.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.34.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 94.139.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.39.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.185.230.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.22.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.216.58.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 84.38.249.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 87.236.33.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.109.62.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a13:1fc0::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a13:1fc0:1::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS213241: AS-TECHIT. 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 (AS213241 isn't in the set, or no route object for AS213241 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 | AS213241 in it | Not covered |
|---|---|---|---|---|---|
| AS-TECHIT | RIPE | 1 | 1 | Yes | 3 |
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.
- ROA: origin3
- Route object: none3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 80.81.192.0/21 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213241 should announce it, add a ROA for AS213241. |
| Route object: none | 80.81.192.0/21 | No route object for it. Add a route object with origin AS213241 in the RIR database for the space. |
| ROA: origin | 80.249.208.0/21 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213241 should announce it, add a ROA for AS213241. |
| Route object: none | 80.249.208.0/21 | Route objects for it name AS1200. Add a route object with origin AS213241 in the RIR database for the space. |
| ROA: origin | 195.66.224.0/21 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213241 should announce it, add a ROA for AS213241. |
| Route object: none | 195.66.224.0/21 | No route object for it. Add a route object with origin AS213241 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS213241 is announced.
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.