bgpreport

Network · data from 2026-11-12

AS213250 ITP-SOLUTIONS

Registry name: ITP-SOLUTIONS Dominic Scholz trading as ITP-Solutions GmbH & Co. KG, DE · PeeringDB

34IPv4 routes 79.4% RPKI valid · 94.1% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
2RPKI invalid 1 origin · 1 maxLength
5No ROA 3 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
17Route objects not announced registered with origin AS213250, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213250, 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.
207.180.58.0/24 Invalid: origin Other origin only 2 0%low visibility 2
5.182.204.0/24 Invalid: maxLength Nonecovered by 5.182.204.0/23 67 10%low visibility 34
45.83.244.0/22 No ROA RIR databaseRIPE 673 100% 67
45.138.48.0/23 No ROA RIR databaseRIPE 673 100% 67
45.138.50.0/23 No ROA RIR databaseRIPE 673 100% 67
91.192.10.0/24 No ROA RIR databaseRIPE 673 100% 67
45.11.228.0/24 No ROA RIR databaseRIPE 672 100% 67
2a01:367:c204::/48 Valid Other origin only 636 100% 67
82.110.105.0/24 Valid Other IRR onlyRADB 673 100% 67
2.56.245.0/24 Valid RIR databaseRIPE 673 100% 67
5.175.166.0/24 Valid RIR databaseRIPE 673 100% 67
5.182.204.0/23 Valid RIR databaseRIPE 673 100% 67
5.182.206.0/23 Valid RIR databaseRIPE 673 100% 67
5.231.108.0/24 Valid RIR databaseRIPE 673 100% 67
5.252.100.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
45.89.124.0/23 Valid RIR databaseRIPE 673 100% 67
45.89.126.0/23 Valid RIR databaseRIPE 673 100% 67
45.131.66.0/23 Valid RIR databaseRIPE 673 100% 67
45.155.172.0/22 Valid RIR databaseRIPE 673 100% 67
64.204.180.0/24 Valid RIR databaseARIN, RADB 673 100% 67
78.108.216.0/24 Valid RIR databaseRIPE 673 100% 67
82.22.102.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
89.42.88.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
89.213.118.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
91.200.100.0/22 Valid RIR databaseRIPE 673 100% 67
95.169.177.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
147.185.197.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.129.85.0/24 Valid RIR databaseRIPE 673 100% 67
185.129.86.0/24 Valid RIR databaseRIPE 673 100% 67
185.234.72.0/24 Valid RIR databaseRIPE 673 100% 67
193.31.28.0/24 Valid RIR databaseRIPE 673 100% 67
193.34.77.0/24 Valid RIR databaseRIPE 673 100% 67
212.87.212.0/23 Valid RIR databaseRIPE 673 100% 67
5.83.132.0/24 Valid RIR databaseRIPE 672 100% 67
45.13.224.0/24 Valid RIR databaseRIPE 672 100% 67
2a0f:580::/29 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS213250's PeeringDB record names no 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 28 are in fix.csv.

  • ROA: origin1
  • ROA: maxLength1
  • ROA: none5
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: origin207.180.58.0/24ROAs covering it name AS834, not AS213250. If AS213250 should announce it, add a ROA for AS213250.2 of 673
Route object: none207.180.58.0/24Route objects for it name AS834. Add a route object with origin AS213250 in the RIR database for the space.2 of 673
ROA: maxLength5.182.204.0/24ROA 5.182.204.0/23 AS213250 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 5.182.204.0/24.67 of 673
Route object: none5.182.204.0/24No route object for it. A route object for 5.182.204.0/23 with origin AS213250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213250 in the RIR database for the space.67 of 673
ROA: none45.83.244.0/22No ROA covers it. Add a ROA for AS213250, maxLength 22.673 of 673
ROA: none45.138.48.0/23No ROA covers it. Add a ROA for AS213250, maxLength 23.673 of 673
ROA: none45.138.50.0/23No ROA covers it. Add a ROA for AS213250, maxLength 23.673 of 673
ROA: none91.192.10.0/24No ROA covers it. Add a ROA for AS213250, maxLength 24.673 of 673
ROA: none45.11.228.0/24No ROA covers it. Add a ROA for AS213250, maxLength 24.672 of 673
Route object: none2a01:367:c204::/48Route objects for it name AS30823. Add a route object with origin AS213250 in the RIR database for the space.636 of 636
Route object: RIR82.110.105.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS213250 whose prefix no peer sees AS213250 announce. Many are kept on purpose (backup routes, space announced only in some places).

5.252.100.0/24RIPEValid
5.252.101.0/24RIPEValid
5.252.102.0/24RIPEValid
5.252.103.0/24RIPEValid
5.253.247.0/24RIPEValid
37.114.37.0/24RIPEValid
37.114.63.0/24RIPEValid
37.221.93.0/24RIPEValid
45.11.229.0/24RIPEValid
45.13.224.0/23RIPEValid
45.86.155.0/24RIPEValid
45.131.64.0/24RIPEValid
45.133.74.0/24RIPEValid
109.71.252.0/24RIPEValid
134.255.236.0/24RIPEValid
194.15.36.0/24RIPEValid
2a0f:b240:1400::/40RIPEValid

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.