bgpreport

Network · data from 2026-11-12

AS25133 McLaut-Invest

Registry name: MCLAUT-AS LLC "McLaut-Invest", UA · PeeringDB

44IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
50Route objects not announced registered with origin AS25133, seen from no peer

Announced routes

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

37.139.160.0/19 Valid RIR databaseRIPE 671 100% 68
45.95.164.0/22 Valid RIR databaseRIPE 671 100% 68
45.143.48.0/22 Valid RIR databaseRIPE 671 100% 68
45.153.208.0/22 Valid RIR databaseRIPE 671 100% 68
45.158.48.0/22 Valid RIR databaseRIPE 671 100% 68
46.255.32.0/22 Valid RIR databaseRIPE 671 100% 68
46.255.36.0/22 Valid RIR databaseRIPE 671 100% 68
78.137.0.0/18 Valid RIR databaseRIPE 671 100% 68
83.142.48.0/22 Valid RIR databaseRIPE 671 100% 68
89.200.232.0/21 Valid RIR databaseRIPE 671 100% 68
91.105.207.0/24 Valid RIR databaseRIPE 671 100% 68
91.211.136.0/22 Valid RIR databaseRIPE 671 100% 68
91.216.106.0/24 Valid RIR databaseRIPE 671 100% 68
91.217.144.0/24 Valid RIR databaseRIPE 671 100% 68
91.244.0.0/18 Valid RIR databaseRIPE 671 100% 68
92.43.80.0/22 Valid RIR databaseRIPE 671 100% 68
92.118.220.0/22 Valid RIR databaseRIPE 671 100% 68
103.237.44.0/22 Valid RIR databaseRIPE 671 100% 68
109.227.64.0/18 Valid RIR databaseRIPE 671 100% 68
152.89.20.0/22 Valid RIR databaseRIPE 671 100% 68
176.67.0.0/19 Valid RIR databaseRIPE 671 100% 68
178.216.16.0/21 Valid RIR databaseRIPE 671 100% 68
185.3.148.0/22 Valid RIR databaseRIPE 671 100% 68
185.41.192.0/22 Valid RIR databaseRIPE 671 100% 68
185.62.96.0/22 Valid RIR databaseRIPE 671 100% 68
185.96.28.0/22 Valid RIR databaseRIPE 671 100% 68
185.103.40.0/22 Valid RIR databaseRIPE 671 100% 68
185.128.92.0/22 Valid RIR databaseRIPE 671 100% 68
185.176.108.0/22 Valid RIR databaseRIPE 671 100% 68
185.176.112.0/22 Valid RIR databaseRIPE 671 100% 68
185.203.244.0/22 Valid RIR databaseRIPE 671 100% 68
185.208.112.0/22 Valid RIR databaseRIPE 671 100% 68
185.228.100.0/22 Valid RIR databaseRIPE 671 100% 68
193.0.240.0/24 Valid RIR databaseRIPE 671 100% 68
193.106.80.0/22 Valid RIR databaseRIPE 671 100% 68
193.254.196.0/24 Valid RIR databaseRIPE 671 100% 68
193.254.197.0/24 Valid RIR databaseRIPE 671 100% 68
194.1.220.0/23 Valid RIR databaseRIPE 671 100% 68
195.95.232.0/23 Valid RIR databaseRIPE 671 100% 68
212.55.64.0/19 Valid RIR databaseRIPE 671 100% 68
213.108.52.0/22 Valid RIR databaseRIPE 671 100% 68
217.115.96.0/21 Valid RIR databaseRIPE 671 100% 68
217.115.104.0/21 Valid RIR databaseRIPE 671 100% 68
103.35.160.0/22 Valid RIR databaseRIPE 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS25133: AS-MCLAUT. 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 (AS25133 isn't in the set, or no route object for AS25133 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.

NameDatabaseASNsSets Route objectsAS25133 in itNot covered
AS-MCLAUT RIPE 51143 Yes 0

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 50 are in fix.csv.

  • Route object: not announced50

Route objects not announced

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

37.139.160.0/22RIPEValid
37.139.164.0/22RIPEValid
37.139.168.0/24RIPEValid
37.139.169.0/24RIPEValid
37.139.170.0/24RIPEValid
37.139.171.0/24RIPEValid
37.139.172.0/24RIPEValid
37.139.173.0/24RIPEValid
37.139.174.0/24RIPEValid
37.139.175.0/24RIPEValid
37.139.176.0/24RIPEValid
37.139.177.0/24RIPEValid
37.139.178.0/24RIPEValid
37.139.179.0/24RIPEValid
37.139.180.0/22RIPEValid
37.139.184.0/22RIPEValid
37.139.188.0/22RIPEValid
46.255.32.0/21RIPENo ROA
78.137.0.0/19RIPEValid
78.137.32.0/24RIPEValid
78.137.33.0/24RIPEValid
78.137.34.0/24RIPEValid
78.137.35.0/24RIPEValid
78.137.36.0/22RIPEValid
78.137.40.0/21RIPEValid
78.137.48.0/20RIPEValid
91.105.206.0/24RIPENo ROA
109.227.64.0/19RIPEValid
109.227.96.0/19RIPEValid
185.3.148.0/24RIPEValid
185.3.149.0/24RIPEValid
185.3.150.0/24RIPEValid
185.3.151.0/24RIPEValid
185.41.192.0/23RIPEValid
185.41.194.0/23RIPEValid
185.103.40.0/23RIPEValid
185.103.42.0/23RIPEValid
185.220.94.0/23RIPEValid
212.55.64.0/22RIPEValid
212.55.68.0/22RIPEValid
212.55.72.0/23RIPEValid
212.55.74.0/23RIPEValid
212.55.76.0/22RIPEValid
212.55.80.0/22RIPEValid
212.55.84.0/23RIPEValid
212.55.86.0/23RIPEValid
212.55.88.0/22RIPEValid
212.55.92.0/22RIPEValid
217.115.96.0/20RIPENo ROA
2a02:c080::/29RIPEValid

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.