bgpreport

Network · data from 2026-11-12

AS29713 ELIA-60

Registry name: ELIA-60 - Reliable Hosting Services, US · PeeringDB

6IPv4 routes 0.0% RPKI valid · 66.7% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
5No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
21Route objects not announced registered with origin AS29713, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29713, 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.
144.172.77.0/24 Invalid: origin Other origin only 27 4%low visibility 22
144.172.121.0/24 Invalid: origin Other origin only 27 4%low visibility 22
199.15.248.0/21 No ROA Other IRR onlyALTDB, NTTCOM 672 100% 67
154.16.219.0/24 No ROA Other IRR onlyNTTCOM 670 100% 67
192.82.109.0/24 No ROA Other IRR onlyALTDB, NTTCOM 670 100% 67
208.73.20.0/22 No ROA Other IRR onlyALTDB, NTTCOM 670 100% 67
2604:4100::/36 No ROA Other IRR onlyNTTCOM 636 100% 67

AS-SET

AS29713'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 35 are in fix.csv.

  • ROA: origin2
  • ROA: none5
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: origin144.172.77.0/24ROAs covering it name AS14956, not AS29713. If AS29713 should announce it, add a ROA for AS29713.27 of 673
Route object: none144.172.77.0/24Route objects for it name AS14956, AS198983. Add a route object with origin AS29713 in the RIR database for the space.27 of 673
ROA: origin144.172.121.0/24ROAs covering it name AS14956, not AS29713. If AS29713 should announce it, add a ROA for AS29713.27 of 673
Route object: none144.172.121.0/24Route objects for it name AS14956. Add a route object with origin AS29713 in the RIR database for the space.27 of 673
ROA: none199.15.248.0/21No ROA covers it. Add a ROA for AS29713, maxLength 21.672 of 673
Route object: RIR199.15.248.0/21Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none154.16.219.0/24No ROA covers it. Add a ROA for AS29713, maxLength 24.670 of 673
Route object: RIR154.16.219.0/24Route object only in NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none192.82.109.0/24No ROA covers it. Add a ROA for AS29713, maxLength 24.670 of 673
Route object: RIR192.82.109.0/24Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none208.73.20.0/22No ROA covers it. Add a ROA for AS29713, maxLength 22.670 of 673
Route object: RIR208.73.20.0/22Route object only in ALTDB, NTTCOM. Add it in the RIR database for the space.670 of 673
ROA: none2604:4100::/36No ROA covers it. Add a ROA for AS29713, maxLength 36.636 of 636
Route object: RIR2604:4100::/36Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.61.136.0/21ALTDB, BBOINo ROA
66.231.178.0/24ALTDB, BBOI, NTTCOMNo ROA
103.230.71.0/24ALTDB, APNIC, BBOIValid
185.240.87.0/24NTTCOMValid
199.15.248.0/22ALTDBNo ROA
199.15.248.0/23ALTDBNo ROA
199.15.248.0/24ALTDBNo ROA
199.15.249.0/24ALTDBNo ROA
199.15.250.0/23ALTDBNo ROA
199.15.250.0/24ALTDBNo ROA
199.15.251.0/24ALTDBNo ROA
199.15.252.0/22ALTDBNo ROA
199.15.252.0/23ALTDBNo ROA
199.15.252.0/24ALTDBNo ROA
199.15.253.0/24ALTDBNo ROA
199.15.254.0/23ALTDBNo ROA
199.15.254.0/24ALTDBNo ROA
199.15.255.0/24ALTDBNo ROA
2606:6680:37::/48NTTCOMNo ROA
2606:6680:38::/48NTTCOMNo ROA
2a0e:be00::/29ALTDB, NTTCOMNo ROA

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.