Network · data from 2026-11-12

AS61608 FORTLINK TELECOM

Registry name: AS61608 - FORTLINK TELECOM, BR · PeeringDB

0IPv4 routes

3IPv6 routes 100.0% RPKI valid · 0.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 3 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS61608, seen from no peer

Announced routes

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


2804:8270::/32	Valid	None	635 100%	67
2804:8270::/33	Valid	None	630 99%	67
2804:8270:8000::/33	Valid	None	630 99%	67

AS-SET

PeeringDB's irr_as_set for AS61608: AS-FORTLINKTELECOM-ALL. 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 (AS61608 isn't in the set, or no route object for AS61608 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.

Name	Database	ASNs	Sets	Route objects	AS61608 in it	Not covered
AS-FORTLINKTELECOM-ALL	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS61608 in it

Not covered

AS-FORTLINKTELECOM-ALL

In no IRR database read today.

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

Route object: none3
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
Route object: none	2804:8270::/32	No route object for it. Add a route object with origin AS61608 in the RIR database for the space.	635 of 636
Route object: none	2804:8270::/33	No route object for it. Add a route object with origin AS61608 in the RIR database for the space.	630 of 636
Route object: none	2804:8270:8000::/33	No route object for it. Add a route object with origin AS61608 in the RIR database for the space.	630 of 636
AS-SET: not found	AS-FORTLINKTELECOM-ALL	PeeringDB names AS-FORTLINKTELECOM-ALL; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

2804:8270::/32

No route object for it. Add a route object with origin AS61608 in the RIR database for the space.

635 of 636

Route object: none

2804:8270::/33

No route object for it. Add a route object with origin AS61608 in the RIR database for the space.

630 of 636

Route object: none

2804:8270:8000::/33

No route object for it. Add a route object with origin AS61608 in the RIR database for the space.

630 of 636

AS-SET: not found

AS-FORTLINKTELECOM-ALL

PeeringDB names AS-FORTLINKTELECOM-ALL; no IRR database read has it.

Route objects not announced

Every route object with origin AS61608 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.