bgpreport

Network · data from 2026-11-12

AS47890 UNMANAGED-DEDICATED-SERVERS UNMANAGED LTD

Registry name: UNMANAGED-DEDICATED-SERVERS UNMANAGED LTD, GB · not in PeeringDB

24IPv4 routes 79.2% RPKI valid · 95.8% with a route object
4IPv6 routes 50.0% RPKI valid · 75.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
6No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
32Route objects not announced registered with origin AS47890, seen from no peer

Announced routes

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

154.214.198.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2.57.120.0/24 No ROA RIR databaseRIPE 670 100% 67
2.57.121.0/24 No ROA RIR databaseRIPE 669 99% 67
80.94.93.0/24 No ROA RIR databaseRIPE 664 99% 67
45.13.37.0/24 No ROA RIR databaseRIPE 663 99% 67
2a10:9100:6::/48 No ROA RIR databaseRIPE 632 99% 67
2a10:9100:a::/48 No ROA RIR databaseRIPE 632 99% 67
2a0e:1d80:7::/48 Valid None 1 0%low visibility 1
154.214.205.0/24 Valid Other IRR onlyRADB 669 99% 67
154.214.213.0/24 Valid Other IRR onlyRADB 669 99% 67
185.232.64.0/24 Valid RIR databaseRIPE 670 100% 67
185.232.66.0/24 Valid RIR databaseRIPE 670 100% 67
193.46.254.0/24 Valid RIR databaseRIPE 670 100% 67
45.13.38.0/24 Valid RIR databaseRIPE 669 99% 67
45.129.15.0/24 Valid RIR databaseRIPE 669 99% 67
45.134.48.0/24 Valid RIR databaseRIPE 669 99% 67
45.138.96.0/24 Valid RIR databaseRIPE 669 99% 67
45.138.97.0/24 Valid RIR databaseRIPE 669 99% 67
45.138.98.0/24 Valid RIR databaseRIPE 669 99% 67
45.148.9.0/24 Valid RIR databaseRIPE 669 99% 67
193.47.69.0/24 Valid RIR databaseRIPE 669 99% 67
193.32.162.0/24 Valid RIR databaseRIPE 663 99% 67
193.46.255.0/24 Valid RIR databaseRIPE 663 99% 67
80.94.92.0/24 Valid RIR databaseRIPE 662 98% 67
80.94.94.0/24 Valid RIR databaseRIPE 662 98% 67
2.57.122.0/24 Valid RIR databaseRIPE 660 98% 67
92.118.39.0/24 Valid RIR databaseRIPE 660 98% 67
2a0c:9f00:2::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

AS47890 isn't in PeeringDB, where networks name their 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 43 are in fix.csv.

  • ROA: origin1
  • ROA: none6
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
ROA: origin154.214.198.0/24ROAs covering it name AS36898, AS328608, not AS47890. If AS47890 should announce it, add a ROA for AS47890.2 of 673
Route object: none154.214.198.0/24Route objects for it name AS36898. Add a route object with origin AS47890 in the RIR database for the space.2 of 673
ROA: none2.57.120.0/24No ROA covers it. Add a ROA for AS47890, maxLength 24.670 of 673
ROA: none2.57.121.0/24No ROA covers it. Add a ROA for AS47890, maxLength 24.669 of 673
ROA: none80.94.93.0/24No ROA covers it. Add a ROA for AS47890, maxLength 24.664 of 673
ROA: none45.13.37.0/24No ROA covers it. Add a ROA for AS47890, maxLength 24.663 of 673
ROA: none2a10:9100:6::/48No ROA covers it. Add a ROA for AS47890, maxLength 48.632 of 636
ROA: none2a10:9100:a::/48No ROA covers it. Add a ROA for AS47890, maxLength 48.632 of 636
Route object: none2a0e:1d80:7::/48No route object for it. Add a route object with origin AS47890 in the RIR database for the space.1 of 636
Route object: RIR154.214.205.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR154.214.213.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

45.13.213.0/24RIPEValid
45.129.14.0/24RIPEValid
86.104.10.0/24RIPEInvalid: origin
154.214.196.0/24RADBValid
154.214.215.0/24RADBValid
154.214.224.0/22RADBValid
154.214.230.0/23RADBValid
154.214.236.0/23RADBValid
154.214.238.0/23RADBValid
154.214.240.0/22RADBValid
154.214.244.0/23RADBValid
154.214.248.0/23RADBValid
154.214.250.0/23RADBValid
200.229.22.0/24ARINInvalid: origin
207.182.48.0/24ALTDBNo ROA
207.182.49.0/24ALTDBNo ROA
207.182.50.0/24ALTDBNo ROA
207.182.51.0/24ALTDBNo ROA
207.182.52.0/24ALTDBNo ROA
207.182.53.0/24ALTDBNo ROA
207.182.54.0/24ALTDBNo ROA
207.182.55.0/24ALTDBNo ROA
207.182.56.0/24ALTDBNo ROA
207.182.57.0/24ALTDBNo ROA
207.182.58.0/24ALTDBNo ROA
207.182.59.0/24ALTDBNo ROA
207.182.60.0/24ALTDBNo ROA
207.182.61.0/24ALTDBNo ROA
207.182.62.0/24ALTDBNo ROA
207.182.63.0/24ALTDBNo ROA
2a0c:9f00::/29RIPENo ROA
2a0c:9f00::/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.