bgpreport

Network · data from 2026-11-12

AS51013 Websupport

Registry name: WEBSUPPORT-SRO-SK-AS WebSupport s.r.o., SK · PeeringDB

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

Announced routes

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

185.87.13.0/24 Valid Nonecovered by 185.87.12.0/22 671 100% 67
37.9.168.0/24 Valid Nonecovered by 37.9.168.0/21 670 100% 67
185.111.88.0/24 Valid Nonecovered by 185.111.88.0/22 668 99% 67
81.95.109.0/24 Valid Nonecovered by 81.95.108.0/23 665 99% 67
92.118.26.0/24 Valid Other origin onlycovered by 92.118.24.0/22 139 21% 43
92.118.27.0/24 Valid Nonecovered by 92.118.24.0/22 139 21% 43
37.9.175.0/24 Valid RIR databaseRIPE 670 100% 67
37.9.168.0/21 Valid RIR databaseRIPE 668 99% 67
45.13.137.0/24 Valid RIR databaseRIPE 667 99% 67
185.87.15.0/24 Valid RIR databaseRIPE 667 99% 67
185.111.89.0/24 Valid RIR databaseRIPE 667 99% 67
92.118.24.0/22 Valid RIR databaseRIPE 666 99% 67
185.87.12.0/22 Valid RIR databaseRIPE 666 99% 67
185.111.88.0/22 Valid RIR databaseRIPE 666 99% 67
185.140.108.0/24 Valid RIR databaseRIPE 666 99% 67
193.32.232.0/24 Valid RIR databaseRIPE 666 99% 67
193.32.233.0/24 Valid RIR databaseRIPE 666 99% 67
193.32.234.0/24 Valid RIR databaseRIPE 666 99% 67
193.32.235.0/24 Valid RIR databaseRIPE 666 99% 67
195.210.28.0/23 Valid RIR databaseRIPE 666 99% 67
213.188.152.0/22 Valid RIR databaseRIPE 666 99% 67
213.188.156.0/23 Valid RIR databaseRIPE 666 99% 67
45.138.185.0/24 Valid RIR databaseRIPE 665 99% 67
81.95.108.0/24 Valid RIR databaseRIPE 665 99% 67
2a00:4b40::/32 Valid RIR databaseRIPE 634 100% 67
2a02:250:2::/48 Valid RIR databaseRIPE 634 100% 67
2a02:4a8:10::/48 Valid RIR databaseRIPE 634 100% 67
92.118.24.0/24 Valid RIR databaseRIPE 139 21% 43

AS-SET

PeeringDB's irr_as_set for AS51013: AS-WEBSUPPORT. 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 (AS51013 isn't in the set, or no route object for AS51013 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 objectsAS51013 in itNot covered
AS-WEBSUPPORT RIPE 3160 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 21 are in fix.csv.

  • Route object: none6
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none185.87.13.0/24No route object for it. A route object for 185.87.12.0/22 with origin AS51013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51013 in the RIR database for the space.671 of 673
Route object: none37.9.168.0/24No route object for it. A route object for 37.9.168.0/21 with origin AS51013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51013 in the RIR database for the space.670 of 673
Route object: none185.111.88.0/24No route object for it. A route object for 185.111.88.0/22 with origin AS51013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51013 in the RIR database for the space.668 of 673
Route object: none81.95.109.0/24No route object for it. A route object for 81.95.108.0/23 with origin AS51013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51013 in the RIR database for the space.665 of 673
Route object: none92.118.26.0/24Route objects for it name AS62292. A route object for 92.118.24.0/22 with origin AS51013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51013 in the RIR database for the space.139 of 673
Route object: none92.118.27.0/24No route object for it. A route object for 92.118.24.0/22 with origin AS51013 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51013 in the RIR database for the space.139 of 673

Route objects not announced

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

45.10.97.0/24RIPEValid
45.81.41.0/24RIPEValid
45.138.184.0/24RIPEValid
45.148.80.0/22RIPENo ROA
81.95.108.0/23RIPEValid
185.87.14.0/24RIPEValid
185.111.90.0/24RIPEValid
185.111.91.0/24RIPEValid
2a00:4b40:1001::/48RIPEValid
2a00:4b40:1337:100::/56RIPEValid
2a00:4b40:4488::/48RIPEValid
2a0e:bb40::/48RIPEValid
2a0e:bb40::/49RIPEInvalid: maxLength
2a0e:bb40::/56RIPEInvalid: maxLength
2a10:bbc0::/32RIPEInvalid: origin

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.