Network · data from 2026-11-12

AS267857 INTEGRA MULTISOLUTIONS

Registry name: AS267857 - INTEGRA MULTISOLUTIONS S.A.S., CO · PeeringDB

10IPv4 routes 70.0% RPKI valid · 70.0% with a route object

1IPv6 routes 0.0% RPKI valid · 0.0% with a route object

2RPKI invalid 0 origin · 2 maxLength

2No ROA 4 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

6Route objects not announced registered with origin AS267857, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267857, 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.


179.49.162.128/26	Invalid: maxLength	Nonecovered by 179.49.162.0/24	2 0%low visibility	2
179.49.162.192/26	Invalid: maxLength	Nonecovered by 179.49.162.0/24	2 0%low visibility	2
2803:bdd0::/32	No ROA	None	636 100%	67
179.49.161.0/24	No ROA	Other IRR onlyRADB	673 100%	67
45.7.135.0/24	Valid	Nonecovered by 45.7.132.0/22	670 100%	67
45.177.109.0/24	Valid	RIR databaseLACNIC, RADB	673 100%	67
45.177.110.0/24	Valid	RIR databaseLACNIC	673 100%	67
179.49.162.0/24	Valid	RIR databaseLACNIC, RADB	673 100%	67
170.79.90.0/23	Valid	RIR databaseLACNIC	672 100%	67
45.173.5.0/24	Valid	RIR databaseLACNIC	670 100%	66
38.19.226.0/24	Valid	RIR databaseARIN	669 99%	67

179.49.162.128/26

Invalid: maxLength

Nonecovered by 179.49.162.0/24

2 0%low visibility

179.49.162.192/26

Invalid: maxLength

Nonecovered by 179.49.162.0/24

2 0%low visibility

2803:bdd0::/32

No ROA

None

636 100%

179.49.161.0/24

No ROA

Other IRR onlyRADB

673 100%

45.7.135.0/24

Valid

Nonecovered by 45.7.132.0/22

670 100%

45.177.109.0/24

Valid

RIR databaseLACNIC, RADB

673 100%

45.177.110.0/24

Valid

RIR databaseLACNIC

673 100%

179.49.162.0/24

Valid

RIR databaseLACNIC, RADB

673 100%

170.79.90.0/23

Valid

RIR databaseLACNIC

672 100%

45.173.5.0/24

Valid

RIR databaseLACNIC

670 100%

38.19.226.0/24

Valid

RIR databaseARIN

669 99%

AS-SET

AS267857'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 15 are in fix.csv.

ROA: maxLength2
ROA: none2
Route object: none4
Route object: RIR1
Route object: not announced6

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	179.49.162.128/26	ROA 179.49.162.0/24 AS267857 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 179.49.162.128/26.	2 of 673
Route object: none	179.49.162.128/26	No route object for it. A route object for 179.49.162.0/24 with origin AS267857 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS267857 in the RIR database for the space.	2 of 673
ROA: maxLength	179.49.162.192/26	ROA 179.49.162.0/24 AS267857 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 179.49.162.192/26.	2 of 673
Route object: none	179.49.162.192/26	No route object for it. A route object for 179.49.162.0/24 with origin AS267857 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS267857 in the RIR database for the space.	2 of 673
ROA: none	2803:bdd0::/32	No ROA covers it. Add a ROA for AS267857, maxLength 32.	636 of 636
Route object: none	2803:bdd0::/32	No route object for it. Add a route object with origin AS267857 in the RIR database for the space.	636 of 636
ROA: none	179.49.161.0/24	No ROA covers it. Add a ROA for AS267857, maxLength 24.	673 of 673
Route object: RIR	179.49.161.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: none	45.7.135.0/24	No route object for it. A route object for 45.7.132.0/22 with origin AS267857 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267857 in the RIR database for the space.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

179.49.162.128/26

ROA 179.49.162.0/24 AS267857 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 179.49.162.128/26.

2 of 673

Route object: none

179.49.162.128/26

No route object for it. A route object for 179.49.162.0/24 with origin AS267857 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS267857 in the RIR database for the space.

2 of 673

ROA: maxLength

179.49.162.192/26

ROA 179.49.162.0/24 AS267857 has maxLength 24; the route is a /26. Raise the maxLength, or add a ROA for 179.49.162.192/26.

2 of 673

Route object: none

179.49.162.192/26

2 of 673

ROA: none

2803:bdd0::/32

No ROA covers it. Add a ROA for AS267857, maxLength 32.

636 of 636

Route object: none

2803:bdd0::/32

No route object for it. Add a route object with origin AS267857 in the RIR database for the space.

636 of 636

ROA: none

179.49.161.0/24

No ROA covers it. Add a ROA for AS267857, maxLength 24.

673 of 673

Route object: RIR

179.49.161.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: none

45.7.135.0/24

No route object for it. A route object for 45.7.132.0/22 with origin AS267857 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267857 in the RIR database for the space.

670 of 673

Route objects not announced

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


45.7.132.0/22	RADB	Valid
45.173.4.0/23	LACNIC, RADB	Valid
45.177.108.0/24	LACNIC, RADB	Valid
45.177.111.0/24	LACNIC	Valid
170.79.88.0/22	LACNIC, RADB	Valid
170.79.89.0/24	LACNIC, RADB	Valid

45.7.132.0/22

RADB

Valid

45.173.4.0/23

LACNIC, RADB

Valid

45.177.108.0/24

LACNIC, RADB

Valid

45.177.111.0/24

LACNIC

Valid

170.79.88.0/22

LACNIC, RADB

Valid

170.79.89.0/24

LACNIC, RADB

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.