bgpreport

Network · data from 2026-11-12

AS55714 Fiberlink

Registry name: APNIC-FIBERLINK-PK - Fiberlink Pvt.Ltd, PK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS55714, 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.
110.34.33.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
110.34.34.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66

AS-SET

AS55714'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 26 are in fix.csv.

  • Route object: not announced26

Route objects not announced

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

103.17.200.0/22RADBNo ROA
103.17.200.0/24APNIC, RADBValid
103.86.36.0/22RADBNo ROA
110.34.32.0/21RADBNo ROA
110.34.35.0/24APNIC, RADBValid
110.34.36.0/24APNICValid
110.34.39.0/24APNICValid
116.204.164.0/22RADBNo ROA
156.238.73.0/24AFRINICInvalid: origin
156.238.74.0/24AFRINICInvalid: origin
156.238.75.0/24AFRINICInvalid: origin
156.238.76.0/24AFRINICInvalid: origin
156.238.77.0/24AFRINICInvalid: origin
156.238.78.0/24AFRINICInvalid: origin
156.238.79.0/24AFRINICInvalid: origin
192.135.90.0/23RADBNo ROA
192.135.90.0/24APNICValid
192.135.91.0/24APNICValid
192.144.78.0/23RADBNo ROA
202.55.128.0/22APNICNo ROA
202.55.128.0/24APNICNo ROA
202.55.129.0/24APNICNo ROA
202.55.130.0/24APNICNo ROA
202.55.131.0/24APNICNo ROA
2406:f500::/32APNICValid
2406:f500::/36APNICValid

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.