bgpreport

Network · data from 2026-11-12

AS271359 AS271359 - SS FIBER TELECOM EIRELI

Registry name: AS271359 - SS FIBER TELECOM EIRELI, BR · not in PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.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
11Route objects not announced registered with origin AS271359, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271359, 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:7a44:10::/44 Valid Nonecovered by 2804:7a44::/35 631 99% 67
200.80.100.0/24 Valid Other IRR onlyALTDB, TC 671 100% 66
200.80.101.0/24 Valid Other IRR onlyALTDB, TC 671 100% 66
200.80.102.0/24 Valid Other IRR onlyALTDB, TC 671 100% 67
200.80.103.0/24 Valid Other IRR onlyALTDB, RADB, TC 670 100% 67
2804:7a44::/32 Valid Other IRR onlyALTDB, RADB, TC 634 100% 67

AS-SET

AS271359 isn't in PeeringDB, where networks name their 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 17 are in fix.csv.

  • Route object: none1
  • Route object: RIR5
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none2804:7a44:10::/44No route object for it. A route object for 2804:7a44::/35 with origin AS271359 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271359 in the RIR database for the space.631 of 636
Route object: RIR200.80.100.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.80.101.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.80.102.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR200.80.103.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:7a44::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

200.80.100.0/22ALTDB, RADB, TCValid
200.80.100.0/23ALTDB, RADB, TCValid
200.80.102.0/23ALTDB, RADB, TCValid
2804:7a44::/35RADBValid
2804:7a44:2000::/35RADBValid
2804:7a44:4000::/35RADBValid
2804:7a44:6000::/35RADBValid
2804:7a44:8000::/35RADBValid
2804:7a44:a000::/35RADBValid
2804:7a44:c000::/35RADBValid
2804:7a44:e000::/35RADBValid

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.