bgpreport

Network · data from 2026-11-12

AS56089 Offratel L@goon

Registry name: OFFRATEL-AS-AP - OFFRATEL, NC · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56089, 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.
203.104.48.0/20 Valid Other origin only 671 100% 67
103.24.112.0/22 Valid RIR databaseAPNIC 672 100% 67
114.69.176.0/20 Valid RIR databaseAPNIC 672 100% 67
175.158.128.0/18 Valid RIR databaseAPNIC 672 100% 67
202.0.157.0/24 Valid RIR databaseAPNIC 672 100% 67
202.166.176.0/21 Valid RIR databaseAPNIC 672 100% 67
202.22.128.0/19 Valid RIR databaseAPNIC 669 99% 67
2404:2a00::/32 Valid RIR databaseAPNIC 636 100% 67

AS-SET

AS56089'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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none203.104.48.0/20Route objects for it name AS18200. Add a route object with origin AS56089 in the RIR database for the space.671 of 673

Route objects not announced

Every route object with origin AS56089 is announced.

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.