bgpreport

Network · data from 2026-11-12

AS214762 MatHost.eu

Registry name: MATHOST Sebastian Stefanek trading as MatHost.eu, PL · PeeringDB

8IPv4 routes 25.0% RPKI valid · 37.5% with a route object
10IPv6 routes 80.0% RPKI valid · 100.0% with a route object
5RPKI invalid 0 origin · 5 maxLength
3No ROA 5 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS214762, seen from no peer

Announced routes

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

87.76.134.0/32 Invalid: maxLength Nonecovered by 87.76.134.0/24 4 1%low visibility 10
87.76.134.1/32 Invalid: maxLength Nonecovered by 87.76.134.0/24 4 1%low visibility 10
89.144.32.0/32 Invalid: maxLength Nonecovered by 89.144.32.0/24 4 1%low visibility 10
89.144.32.255/32 Invalid: maxLength Nonecovered by 89.144.32.0/24 4 1%low visibility 10
145.79.141.0/32 Invalid: maxLength Nonecovered by 145.79.141.0/24 4 1%low visibility 10
44.30.200.0/24 No ROA Other IRR onlyRADB 672 100% 66
2a05:dfc1:1410::/44 No ROA RIR databaseRIPE 634 100% 69
2a0f:85c1:80b::/48 No ROA RIR databaseRIPE 634 100% 69
145.79.141.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
89.144.32.0/24 Valid RIR databaseRIPE 671 100% 67
2a06:1283:8904::/48 Valid RIR databaseRIPE 634 100% 69
2a06:1283:890c::/48 Valid RIR databaseRIPE 634 100% 69
2a07:54c1:c000::/44 Valid RIR databaseRIPE 634 100% 69
2a0f:b240:5c00::/40 Valid RIR databaseRIPE 634 100% 69
2a13:9500:53::/48 Valid RIR databaseRIPE 634 100% 69
2a13:c8c4:1000::/36 Valid RIR databaseRIPE 634 100% 69
2a13:c8c4:ff00::/40 Valid RIR databaseRIPE 632 99% 69
2a14:7580:ff9c::/48 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS214762: AS214762:AS-MH. 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 (AS214762 isn't in the set, or no route object for AS214762 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 objectsAS214762 in itNot covered
AS214762:AS-MH RIPE1 member set in no database: AS199746:AS-NEXTSERV 244732,774 Yes 5

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

  • ROA: maxLength5
  • ROA: none3
  • Route object: none5
  • Route object: RIR1
  • AS-SET: missing member1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength87.76.134.0/32ROA 87.76.134.0/24 AS214762 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 87.76.134.0/32.4 of 673
Route object: none87.76.134.0/32No route object for it. A route object for 87.76.134.0/24 with origin AS214762 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214762 in the RIR database for the space.4 of 673
ROA: maxLength87.76.134.1/32ROA 87.76.134.0/24 AS214762 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 87.76.134.1/32.4 of 673
Route object: none87.76.134.1/32No route object for it. A route object for 87.76.134.0/24 with origin AS214762 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214762 in the RIR database for the space.4 of 673
ROA: maxLength89.144.32.0/32ROA 89.144.32.0/24 AS214762 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 89.144.32.0/32.4 of 673
Route object: none89.144.32.0/32No route object for it. A route object for 89.144.32.0/24 with origin AS214762 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214762 in the RIR database for the space.4 of 673
ROA: maxLength89.144.32.255/32ROA 89.144.32.0/24 AS214762 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 89.144.32.255/32.4 of 673
Route object: none89.144.32.255/32No route object for it. A route object for 89.144.32.0/24 with origin AS214762 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214762 in the RIR database for the space.4 of 673
ROA: maxLength145.79.141.0/32ROA 145.79.141.0/24 AS214762 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 145.79.141.0/32.4 of 673
Route object: none145.79.141.0/32No route object for it. A route object for 145.79.141.0/24 with origin AS214762 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS214762 in the RIR database for the space.4 of 673
ROA: none44.30.200.0/24No ROA covers it. Add a ROA for AS214762, maxLength 24.672 of 673
Route object: RIR44.30.200.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2a05:dfc1:1410::/44No ROA covers it. Add a ROA for AS214762, maxLength 44.634 of 636
ROA: none2a0f:85c1:80b::/48No ROA covers it. Add a ROA for AS214762, maxLength 48.634 of 636
AS-SET: missing memberAS214762:AS-MHAS214762:AS-MH (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

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

87.76.134.0/24RIPEValid
89.144.44.0/24RIPEValid
2a14:7581:5116::/48RIPEValid
2a14:7581:5117::/48RIPEValid
2a14:7581:5118::/48RIPEValid

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.