bgpreport

Network · data from 2026-11-12

AS147049 PacketHub AS147049

Registry name: PACKETHUBSA-AS-AP - PacketHub S.A., AU · PeeringDB

101IPv4 routes 99.0% RPKI valid · 97.0% with a route object
61IPv6 routes 98.4% RPKI valid · 98.4% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 4 with no route object for this origin
40Low visibility seen by under 10% of full-table peers
22Route objects not announced registered with origin AS147049, seen from no peer

Announced routes

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

45.13.235.0/24 Invalid: origin None 2 0%low visibility 2
2a13:240:b600::/40 Invalid: origin Other origin only 0 0%low visibility 1
192.166.246.0/24 Valid None 2 0%low visibility 2
192.166.247.0/24 Valid None 2 0%low visibility 2
86.38.66.0/24 Valid RIR databaseRIPE 673 100% 67
86.38.69.0/24 Valid RIR databaseRIPE 673 100% 67
86.38.77.0/24 Valid RIR databaseRIPE 673 100% 67
86.38.78.0/24 Valid RIR databaseRIPE 673 100% 67
86.38.79.0/24 Valid RIR databaseRIPE 673 100% 67
86.38.90.0/24 Valid RIR databaseRIPE 673 100% 67
86.38.94.0/24 Valid RIR databaseRIPE 673 100% 67
86.38.95.0/24 Valid RIR databaseRIPE 673 100% 67
89.117.202.0/24 Valid RIR databaseRIPE 673 100% 67
89.117.205.0/24 Valid RIR databaseRIPE 673 100% 67
89.117.210.0/24 Valid RIR databaseRIPE 673 100% 67
89.117.232.0/24 Valid RIR databaseRIPE 673 100% 67
116.204.193.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
116.204.194.0/24 Valid RIR databaseAPNIC 673 100% 67
116.204.195.0/24 Valid RIR databaseAPNIC 673 100% 67
185.135.45.0/24 Valid RIR databaseRIPE 673 100% 67
186.247.37.0/24 Valid RIR databaseRIPE 673 100% 67
186.247.38.0/24 Valid RIR databaseRIPE 673 100% 67
186.247.39.0/24 Valid RIR databaseRIPE 673 100% 67
186.247.40.0/24 Valid RIR databaseRIPE 673 100% 67
186.247.41.0/24 Valid RIR databaseRIPE 673 100% 67
186.247.47.0/24 Valid RIR databaseRIPE 673 100% 67
186.247.175.0/24 Valid RIR databaseRIPE 673 100% 66
187.13.6.0/24 Valid RIR databaseRIPE 673 100% 66
187.13.10.0/24 Valid RIR databaseRIPE 673 100% 66
187.13.252.0/24 Valid RIR databaseRIPE 673 100% 67
187.13.253.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.57.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.60.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.61.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.62.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.63.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.87.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.88.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.248.0/24 Valid RIR databaseRIPE 673 100% 67
187.14.249.0/24 Valid RIR databaseRIPE 673 100% 67
187.15.99.0/24 Valid RIR databaseRIPE 673 100% 67
187.15.103.0/24 Valid RIR databaseRIPE 673 100% 67
187.15.107.0/24 Valid RIR databaseRIPE 673 100% 67
187.15.108.0/24 Valid RIR databaseRIPE 673 100% 67
187.15.142.0/24 Valid RIR databaseRIPE 673 100% 67
187.15.154.0/24 Valid RIR databaseRIPE 673 100% 67
187.15.155.0/24 Valid RIR databaseRIPE 673 100% 67
187.40.227.0/24 Valid RIR databaseRIPE 673 100% 67
187.40.234.0/24 Valid RIR databaseRIPE 673 100% 67
187.40.235.0/24 Valid RIR databaseRIPE 673 100% 67
187.40.240.0/24 Valid RIR databaseRIPE 673 100% 66
103.173.150.0/24 Valid RIR databaseAPNIC 672 100% 66
186.247.171.0/24 Valid RIR databaseRIPE 672 100% 66
187.15.121.0/24 Valid RIR databaseRIPE 672 100% 68
187.40.232.0/24 Valid RIR databaseRIPE 672 100% 67
187.15.92.0/24 Valid RIR databaseRIPE 671 100% 67
187.15.93.0/24 Valid RIR databaseRIPE 671 100% 67
187.15.94.0/24 Valid RIR databaseRIPE 671 100% 67
187.15.95.0/24 Valid RIR databaseRIPE 671 100% 67
187.15.96.0/24 Valid RIR databaseRIPE 671 100% 67
187.15.122.0/24 Valid RIR databaseRIPE 671 100% 68
187.13.243.0/24 Valid RIR databaseRIPE 670 100% 67
187.13.244.0/24 Valid RIR databaseRIPE 670 100% 67
187.15.98.0/24 Valid RIR databaseRIPE 670 100% 67
187.15.141.0/24 Valid RIR databaseRIPE 670 100% 67
187.15.153.0/24 Valid RIR databaseRIPE 670 100% 67
2407:e8c0:1::/48 Valid RIR databaseAPNIC 636 100% 67
2407:e8c0:7::/48 Valid RIR databaseAPNIC 636 100% 68
2407:e8c0:c::/48 Valid RIR databaseAPNIC 636 100% 67
2407:e8c0:24::/48 Valid RIR databaseAPNIC 636 100% 67
2407:e8c0:25::/48 Valid RIR databaseAPNIC 636 100% 67
2a13:240:6300::/40 Valid RIR databaseRIPE 636 100% 69
2407:e8c0::/48 Valid RIR databaseAPNIC 635 100% 69
2407:e8c0:4::/48 Valid RIR databaseAPNIC 635 100% 69
2407:e8c0:8::/48 Valid RIR databaseAPNIC 635 100% 67
2407:e8c0:d::/48 Valid RIR databaseAPNIC 635 100% 67
2407:e8c0:f::/48 Valid RIR databaseAPNIC 635 100% 70
2407:e8c0:21::/48 Valid RIR databaseAPNIC 635 100% 67
2407:e8c0:22::/48 Valid RIR databaseAPNIC 635 100% 69
2407:e8c0:26::/48 Valid RIR databaseAPNIC 635 100% 67
2407:e8c0:5700::/40 Valid RIR databaseAPNIC 635 100% 69
2407:e8c0:6000::/40 Valid RIR databaseAPNIC 635 100% 67
2a13:240:3800::/40 Valid RIR databaseRIPE 635 100% 70
2407:e8c0:2::/48 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:3::/48 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:5::/48 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:6::/48 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:a::/48 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:b::/48 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:e::/48 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:11::/48 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:12::/48 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:13::/48 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:1f::/48 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:20::/48 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:23::/48 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:4a00::/40 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:5600::/40 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:5800::/40 Valid RIR databaseAPNIC 634 100% 68
2407:e8c0:5a00::/40 Valid RIR databaseAPNIC 634 100% 67
2407:e8c0:5b00::/40 Valid RIR databaseAPNIC 634 100% 68
2a13:240:2100::/40 Valid RIR databaseRIPE 634 100% 67
2a13:240:2900::/40 Valid RIR databaseRIPE 634 100% 67
2a13:240:3100::/40 Valid RIR databaseRIPE 634 100% 68
2a13:240:3300::/40 Valid RIR databaseRIPE 634 100% 67
2a13:240:4000::/40 Valid RIR databaseRIPE 634 100% 67
2a13:240:5800::/40 Valid RIR databaseRIPE 634 100% 67
2a13:240:5b00::/40 Valid RIR databaseRIPE 634 100% 69
2407:e8c0:9::/48 Valid RIR databaseAPNIC 633 100% 68
2a13:240:6e00::/40 Valid RIR databaseRIPE 633 100% 67
2a13:240:7100::/40 Valid RIR databaseRIPE 633 100% 67
2a13:240:7200::/40 Valid RIR databaseRIPE 633 100% 67
2a13:240:9300::/40 Valid RIR databaseRIPE 633 100% 67
2a13:240:b700::/40 Valid RIR databaseRIPE 633 100% 67
2a13:240:1500::/40 Valid RIR databaseRIPE 632 99% 68
2a13:240:1600::/40 Valid RIR databaseRIPE 632 99% 68
2a13:240:1700::/40 Valid RIR databaseRIPE 632 99% 68
2a13:240:7a00::/40 Valid RIR databaseRIPE 632 99% 67
2a13:240:7c00::/40 Valid RIR databaseRIPE 632 99% 67
2a13:240:8700::/40 Valid RIR databaseRIPE 632 99% 68
2a13:240:8c00::/40 Valid RIR databaseRIPE 632 99% 67
2a13:240:9100::/40 Valid RIR databaseRIPE 632 99% 68
2a13:240:9200::/40 Valid RIR databaseRIPE 632 99% 67
2a13:240:b800::/40 Valid RIR databaseRIPE 632 99% 67
2a13:240:2c00::/40 Valid RIR databaseRIPE 631 99% 68
2a13:240:8d00::/40 Valid RIR databaseRIPE 631 99% 68
185.213.83.0/24 Valid RIR databaseRADB, RIPE 11 2%low visibility 10
169.40.8.0/24 Valid RIR databaseRIPE 3 0%low visibility 2
5.180.61.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
31.222.254.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
45.88.190.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
45.90.222.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
45.94.210.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
45.134.224.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
62.3.36.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
89.147.101.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
94.156.149.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
94.156.205.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
153.92.40.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
157.97.134.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
160.238.37.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
176.100.43.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
176.227.243.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.153.179.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.172.52.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.172.53.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.213.80.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.213.82.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.216.231.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.219.141.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.229.59.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.255.130.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
192.166.244.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
193.29.61.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
193.36.237.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
194.233.96.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
212.15.80.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
212.15.81.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
212.15.82.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
212.15.83.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
212.15.84.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
217.216.105.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS147049: APNIC::AS-SET-AS147049. 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 (AS147049 isn't in the set, or no route object for AS147049 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 objectsAS147049 in itNot covered
APNIC::AS-SET-AS147049 APNIC 511,036 Yes 4

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

  • ROA: origin2
  • Route object: none4
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
ROA: origin45.13.235.0/24ROAs covering it name AS51167, not AS147049. If AS147049 should announce it, add a ROA for AS147049.2 of 673
Route object: none45.13.235.0/24No route object for it. Add a route object with origin AS147049 in the RIR database for the space.2 of 673
ROA: origin2a13:240:b600::/40ROAs covering it name AS207137, not AS147049. If AS147049 should announce it, add a ROA for AS147049.0 of 636
Route object: none2a13:240:b600::/40Route objects for it name AS207137. Add a route object with origin AS147049 in the RIR database for the space.0 of 636
Route object: none192.166.246.0/24No route object for it. Add a route object with origin AS147049 in the RIR database for the space.2 of 673
Route object: none192.166.247.0/24No route object for it. Add a route object with origin AS147049 in the RIR database for the space.2 of 673

Route objects not announced

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

103.173.150.0/23APNICValid
169.40.9.0/24RIPEValid
169.40.10.0/24RIPEValid
169.40.11.0/24RIPEValid
172.216.248.0/24RIPEValid
172.216.251.0/24RIPEValid
172.216.252.0/24RIPEValid
194.156.136.0/24RIPEValid
212.15.85.0/24RIPEValid
217.216.61.0/24RIPEValid
2001:470:409::/48ARINValid
2407:e8c0:4b00::/40APNICValid
2407:e8c0:4c00::/40APNICValid
2407:e8c0:4d00::/40APNICValid
2407:e8c0:4e00::/40APNICValid
2407:e8c0:4f00::/40APNICValid
2407:e8c0:5000::/40APNICValid
2407:e8c0:5100::/40APNICValid
2407:e8c0:5200::/40APNICValid
2407:e8c0:5300::/40APNICValid
2407:e8c0:5400::/40APNICValid
2407:e8c0:5500::/40APNICValid

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.